Kernel memory leak via incomplete controller cleanup
Published Dec 9, 2025 · Updated May 23, 2026
A memory leak in the hpsa SCSI driver in affected Linux kernel versions allows local users to reduce availability during controller initialization. When alloc_percpu() fails in hpsa_init_one(), the clean1 path frees the controller structure directly but leaves its reply_map allocation unreleased. Reachability requires hpsa controller initialization while the per-CPU allocation fails; published evidence reports leaked kernel memory, not a demonstrated crash or privilege gain.
Summary
What happened
A memory leak in the hpsa SCSI driver in affected Linux kernel versions allows local users to reduce availability during controller initialization. When alloc_percpu() fails in hpsa_init_one(), the clean1 path frees the controller structure directly but leaves its reply_map allocation unreleased. Reachability requires hpsa controller initialization while the per-CPU allocation fails; published evidence reports leaked kernel memory, not a demonstrated crash or privilege gain.
The record
- CVE
- CVE-2022-50646
- Published
- Dec 9, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1edd825c11f8ed2c409d6fb6b3d90a042cbf738d
- Affected versionversion=4.14.63 <4.15
- Affected versionversion=4.16
- Affected versionversion=8b834bff1b73dce46f4e9f5e84af6f73fed8b0ef <0aa7be66168b1e84b2581ffff3ccb54a6c804a1e
- Affected versionversion=8b834bff1b73dce46f4e9f5e84af6f73fed8b0ef <9c9ff300e0de07475796495d86f449340d454a0c
- Affected versionversion=8b834bff1b73dce46f4e9f5e84af6f73fed8b0ef <bfe10a1d9fbccdf39f8449d62509f070d8aaaac1
- Affected versionversion=8b834bff1b73dce46f4e9f5e84af6f73fed8b0ef <c808edbf580bfc454671cbe66e9d7c2e938e7601
- Affected versionversion=8b834bff1b73dce46f4e9f5e84af6f73fed8b0ef <f4d1c14e8b404766ff2bb8644bb19443d73965de
- Affected versionversion=8b834bff1b73dce46f4e9f5e84af6f73fed8b0ef <f8fc2f18652917cdcc89cb23f3a1b7cb6e119c5e
- Affected versionversion=8b834bff1b73dce46f4e9f5e84af6f73fed8b0ef <fc998d0a7d65672f0812f11cd0ec4bbe4f8f8507
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo