CVE-2022-50420: crypto: hisilicon/hpre - fix resource leak in remove process
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2b3e3ecdb402ff1053ee25b598ff21b9ddf4384f, 45e6319bd5f2154d8b8c9f1eaa4ac030ba0d330c, 4e0de941d252d4e7c985981e78480c8d6f020b64.
Low priority for now. Upgrade to Linux Linux 2b3e3ecdb402ff1053ee25b598ff21b9ddf4384f, 45e6319bd5f2154d8b8c9f1eaa4ac030ba0d330c, 4e0de941d252d4e7c985981e78480c8d6f020b64 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: crypto: hisilicon/hpre - fix resource leak in remove process In hpre_remove(), when the disable operation of qm sriov failed, the following logic should continue to be executed to release the remaining resources that have been allocated, instead of returning directly, otherwise there will be resource leakage.
- Published
- Oct 1, 2025
- Updated
- Aug 15, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-401
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.5affected
- 5ec302a364bfd95be29a9784b2fabd8e2ddf0476 and later · before 2b3e3ecdb402ff1053ee25b598ff21b9ddf4384faffected · git
- 5ec302a364bfd95be29a9784b2fabd8e2ddf0476 and later · before 4e0de941d252d4e7c985981e78480c8d6f020b64affected · git
- 5ec302a364bfd95be29a9784b2fabd8e2ddf0476 and later · before cb873c93a7ad27681920bf062ef052fca1e8d5b1affected · git
- 5ec302a364bfd95be29a9784b2fabd8e2ddf0476 and later · before 45e6319bd5f2154d8b8c9f1eaa4ac030ba0d330caffected · git
- before 5.5not affected · semver
- 5.15.86 and later · up to and including 5.15.*not affected · semver
- 6.0.16 and later · up to and including 6.0.*not affected · semver
- 6.1.2 and later · up to and including 6.1.*not affected · semver
- 6.2 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.5 and later · before 5.15.86
- linux linux kernel5.16 and later · before 6.0.16
- linux linux kernel6.1 and later · before 6.1.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.4-1 | 6.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-39902Oct 1, 2025 · mm/slub: avoid accessing metadata when pointer is invalid in object_err()22Monitor
- ← EarlierCVE-2025-39903Oct 1, 2025 · of_numa: fix uninitialized memory nodes causing kernel panic22Monitor
- Later →CVE-2025-39904Oct 1, 2025 · arm64: kexec: initialize kexec_buf struct in load_other_segments()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2b3e3ecdb402ff1053ee25b598ff21b9ddf4384f | Vendor (CNA) |
| Linux Linux | 45e6319bd5f2154d8b8c9f1eaa4ac030ba0d330c | Vendor (CNA) |
| Linux Linux | 4e0de941d252d4e7c985981e78480c8d6f020b64 | Vendor (CNA) |
| Linux Linux | cb873c93a7ad27681920bf062ef052fca1e8d5b1 | Vendor (CNA) |
| debian:linux | 6.1.4-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.