CVE-2024-53096: mm: resolve faulty mmap_region() error path behaviour
Noroxi assessment
Priority: Monitor (action score 31/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.33% (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 43323a4e5b3f8ccc08e2f835abfdc7ee9da8f6ed, 44f48eb9a6051826227bbd375446064fb2a43c6c, 5.10.231; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; cbl2 kernel 5.15.173.1-2 on CBL Mariner 2.0 5.15.176.3-1.
Low priority for now. Upgrade to Linux Linux 43323a4e5b3f8ccc08e2f835abfdc7ee9da8f6ed, 44f48eb9a6051826227bbd375446064fb2a43c6c, 5.10.231; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; cbl2 kernel 5.15.173.1-2 on CBL Mariner 2.0 5.15.176.3-1 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: mm: resolve faulty mmap_region() error path behaviour The mmap_region() function is somewhat terrifying, with spaghetti-like control flow and numerous means by which issues can arise and incomplete state, memory leaks and other unpleasantness can occur. A large amount of the complexity arises from trying to handle errors late in the process of mapping a VMA, which forms the basis of recently observed issues with resource leaks and observable inconsistent state. Taking advantage of previous patches in this series we move a number of checks earlier in the code, simplifying things by moving the core of the logic into a static internal function __mmap_region(). Doing this allows us to perform a number of checks up front before we do any real work, and allows us to unwind the writable unmap check unconditionally as required and to perform a CONFIG_DEBUG_VM_MAPLE_TREE validation unconditionally also. We move a number of things here: 1. We preallocate memory for the iterator before we call the file-backed memory hook, allowing us to exit early and avoid having to perform complicated and error-prone close/free logic. We carefully free iterator state on both success and error paths. 2. The enclosing mmap_region() function handles the mapping_map_writable() logic early. Previously the logic had the mapping_map_writable() at the point of mapping a newly allocated file-backed VMA, and a matching mapping_unmap_writable() on success and error paths. We now do this unconditionally if this is a file-backed, shared writable mapping. If a driver changes the flags to eliminate VM_MAYWRITE, however doing so does not invalidate the seal check we just performed, and we in any case always decrement the counter in the wrapper. We perform a debug assert to ensure a driver does not attempt to do the opposite. 3. We also move arch_validate_flags() up into the mmap_region() function. This is only relevant on arm64 and sparc64, and the check is only meaningful for SPARC with ADI enabled. We explicitly add a warning for this arch if a driver invalidates this check, though the code ought eventually to be fixed to eliminate the need for this. With all of these measures in place, we no longer need to explicitly close the VMA on error paths, as we place all checks which might fail prior to a call to any driver mmap hook. This eliminates an entire class of errors, makes the code easier to reason about and more robust.
- Published
- Nov 25, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.3% · 27th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
- 6757330b1be5b0606125b65ed50caac69bccf9a5, 66f2ed0172af04a89677ae1898600e1264e25800, 6.1affected
- a3c08c021778dad30f69895e378843e9f423d734 and later · before 43323a4e5b3f8ccc08e2f835abfdc7ee9da8f6edaffected · git
- 43bed0a13a5cdbb314d14f28c2bf2c60eb4e6e1e and later · before 44f48eb9a6051826227bbd375446064fb2a43c6caffected · git
- deb0f6562884b5b4beb883d73e66a7d3a1b96d99 and later · before 52c81fd0f5a8bf8032687b94ccf00d13b44cc5c8affected · git
- deb0f6562884b5b4beb883d73e66a7d3a1b96d99 and later · before bdc136e2b05fabcd780fe5f165d154eb779dfcb0affected · git
- deb0f6562884b5b4beb883d73e66a7d3a1b96d99 and later · before 5de195060b2e251a835f622759550e6202167641affected · git
- 5.10.150 and later · before 5.10.231affected · semver
- 5.15.75 and later · before 5.15.174affected · semver
- 5.19.17 and later · before 5.20affected · semver
- 6.0.3 and later · before 6.1affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.10.150 and later · before 5.10.231
- linux linux kernel5.15.75 and later · before 5.15.174
- linux linux kernel6.0.3 and later · before 6.1.119
- linux linux kernel6.2 and later · before 6.6.63
- linux linux kernel6.7 and later · before 6.12
- linux linux kernel5.19.17
- linux linux kernel6.12
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.119-1 | 6.1.119-1 |
| Debian:13 | linux | before 6.12.3-1 | 6.12.3-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-2024-53094Nov 21, 2024 · RDMA/siw: Add sendpage_ok() check to disable MSG_SPLICE_PAGES22Monitor
- ← EarlierCVE-2024-53095Nov 21, 2024 · smb: client: Fix use-after-free of network namespace.39Monitor
- Later →CVE-2024-53097Nov 25, 2024 · mm: krealloc: Fix MTE false alarm in __do_krealloc22Monitor
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 | 43323a4e5b3f8ccc08e2f835abfdc7ee9da8f6ed | Vendor (CNA) |
| Linux Linux | 44f48eb9a6051826227bbd375446064fb2a43c6c | Vendor (CNA) |
| Linux Linux | 5.10.231 | Vendor (CNA) |
| Linux Linux | 5.15.174 | Vendor (CNA) |
| Linux Linux | 5.20 | Vendor (CNA) |
| Linux Linux | 52c81fd0f5a8bf8032687b94ccf00d13b44cc5c8 | Vendor (CNA) |
| Linux Linux | 5de195060b2e251a835f622759550e6202167641 | Vendor (CNA) |
| Linux Linux | 6.1 | Vendor (CNA) |
| Linux Linux | bdc136e2b05fabcd780fe5f165d154eb779dfcb0 | Vendor (CNA) |
| azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-2 on CBL Mariner 2.0 | 5.15.176.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.119-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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 (6 more)Show less
- git.kernel.org/stable/c/44f48eb9a6051826227bbd375446064fb2a43c6c
- git.kernel.org/stable/c/52c81fd0f5a8bf8032687b94ccf00d13b44cc5c8
- git.kernel.org/stable/c/5de195060b2e251a835f622759550e6202167641
- git.kernel.org/stable/c/bdc136e2b05fabcd780fe5f165d154eb779dfcb0
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.