Local memory exhaustion via uninitialized mpol_new reference count
Published Feb 26, 2025 · Updated May 11, 2026
Memory leak in mm/mempolicy.c in affected Linux kernel releases allows local users to exhaust memory through concurrent mbind calls. shared_policy_replace allocates mpol_new, drops sp->lock, and can pass the unused object to mpol_put before initializing its reference count, preventing correct release. Triggering the leak requires many processes to update policy on the same shared-memory file during the allocation window, allowing memory exhaustion and service interruption.
Summary
What happened
Memory leak in mm/mempolicy.c in affected Linux kernel releases allows local users to exhaust memory through concurrent mbind calls. shared_policy_replace allocates mpol_new, drops sp->lock, and can pass the unused object to mpol_put before initializing its reference count, preventing correct release. Triggering the leak requires many processes to update policy on the same shared-memory file during the allocation window, allowing memory exhaustion and service interruption.
The record
- CVE
- CVE-2022-49080
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=3.8
- Affected versionversion=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <198932a14aeb19a15cf19e51e151d023bc4cd648
- Affected versionversion=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <25f506273b6ae806fd46bfcb6fdaa5b9ec81a05b
- Affected versionversion=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <39a32f3c06f6d68a530bf9612afa19f50f12e93d
- Affected versionversion=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <4ad099559b00ac01c3726e5c95dc3108ef47d03e
- Affected versionversion=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <5e16dc5378abd749a836daa9ee4ab2c8d2668999
- Affected versionversion=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <6e00309ac716fa8225f0cbde2cd9c24f0e74ee21
- Affected versionversion=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <8510c2346d9e47a72b7f018a36ef0c39483e53d6
- Affected versionversion=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <f7e183b0a7136b6dc9c7b9b2a85a608a8feba894
- Affected versionversion=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <fe39ac59dbbf893b73b24e3184161d0bd06d6651
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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