CVE-2024-47674: mm: avoid leaving partial pfn mappings around in error case
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.24% (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 3213fdcab961026203dd587a4533600c70b3336b, 35770ca6180caa24a2b258c99a87bd437a1ee10f, 5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.56.1-5; azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 6.6.56.1-5.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3213fdcab961026203dd587a4533600c70b3336b, 35770ca6180caa24a2b258c99a87bd437a1ee10f, 5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.56.1-5; azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 6.6.56.1-5 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: avoid leaving partial pfn mappings around in error case As Jann points out, PFN mappings are special, because unlike normal memory mappings, there is no lifetime information associated with the mapping - it is just a raw mapping of PFNs with no reference counting of a 'struct page'. That's all very much intentional, but it does mean that it's easy to mess up the cleanup in case of errors. Yes, a failed mmap() will always eventually clean up any partial mappings, but without any explicit lifetime in the page table mapping itself, it's very easy to do the error handling in the wrong order. In particular, it's easy to mistakenly free the physical backing store before the page tables are actually cleaned up and (temporarily) have stale dangling PTE entries. To make this situation less error-prone, just make sure that any partial pfn mapping is torn down early, before any other error handling.
- BDU:2025-00021
- SUSE-SU-2024:4038-1
- SUSE-SU-2025:03097-1
- SUSE-SU-2025:03108-1
- SUSE-SU-2025:03124-1
- SUSE-SU-2025:03130-1
- SUSE-SU-2025:03135-1
- SUSE-SU-2025:03156-1
- SUSE-SU-2025:03175-1
- SUSE-SU-2025:03181-1
- SUSE-SU-2025:03186-1
- SUSE-SU-2025:03190-1
- SUSE-SU-2025:03191-1
- SUSE-SU-2025:03209-1
- SUSE-SU-2025:03223-1
- SUSE-SU-2025:03226-1
- SUSE-SU-2025:20698-1
- SUSE-SU-2025:20703-1
- SUSE-SU-2025:20711-1
- SUSE-SU-2025:20714-1
- Published
- Oct 15, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-459
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.15.168
- linux linux kernel5.16 and later · before 6.1.111
- linux linux kernel6.2 and later · before 6.6.52
- linux linux kernel6.7 and later · before 6.10.11
- linux linux kernel6.11
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.13affected
- b97a50adb37e98b940a30c4656565ff609aa8f94 and later · before 3213fdcab961026203dd587a4533600c70b3336baffected · git
- 69d4e1ce9087c8767f2fe9b9426fa2755c8e9072 and later · before 35770ca6180caa24a2b258c99a87bd437a1ee10faffected · git
- 74ffa5a3e68504dd289135b1cf0422c19ffb3f2e and later · before 5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959affected · git
- 74ffa5a3e68504dd289135b1cf0422c19ffb3f2e and later · before 65d0db500d7c07f0f76fc24a4d837791c4862cd2affected · git
- 74ffa5a3e68504dd289135b1cf0422c19ffb3f2e and later · before a95a24fcaee1b892e47d5e6dcc403f713874ee80affected · git
- 74ffa5a3e68504dd289135b1cf0422c19ffb3f2e and later · before 954fd4c81f22c4b6ba65379a81fd252971bf4ef3affected · git
- 74ffa5a3e68504dd289135b1cf0422c19ffb3f2e and later · before 79a61cc3fc0466ad2b7b89618a6157785f0293b3affected · git
- before 5.13not affected · semver
- 5.15.168 and later · up to and including 5.15.*not affected · semver
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.112-1 | 6.1.112-1 |
| Debian:13 | linux | before 6.10.11-1 | 6.10.11-1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_60 | before 15-2.1 | 15-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_61 | before 18-4.1 | 18-4.1 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_47 | before 17-150300.2.1 | 17-150300.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_49 | before 15-150300.2.1 | 15-150300.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_29 | before 16-150400.2.1 | 16-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_31 | before 14-150400.2.1 | 14-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_32 | before 14-150400.2.1 | 14-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_17 | before 16-150500.2.1 | 16-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_19 | before 14-150500.2.1 | 14-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_20 | before 14-150500.2.1 | 14-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_3 | before 20-150600.2.1 | 20-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_4 | before 16-150600.2.1 | 16-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_5 | before 15-150600.2.1 | 15-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_0 | before 21-150600.3.1 | 21-150600.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_1 | before 20-150600.2.1 | 20-150600.2.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-default | before 3.0.101-108.168.1 | 3.0.101-108.168.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-ec2 | before 3.0.101-108.168.1 | 3.0.101-108.168.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-source | before 3.0.101-108.168.1 | 3.0.101-108.168.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-syms | before 3.0.101-108.168.1 | 3.0.101-108.168.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-trace | before 3.0.101-108.168.1 | 3.0.101-108.168.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-xen | before 3.0.101-108.168.1 | 3.0.101-108.168.1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0_Update_2 | before 11-1.1 | 11-1.1 |
+3
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-47661Oct 9, 2024 · drm/amd/display: Avoid overflow from uint32_t to uint8_t22Monitor
- ← EarlierCVE-2024-47664Oct 9, 2024 · spi: hisi-kunpeng: Add verification for the max_frequency provided by the firmware22Monitor
- Later →CVE-2024-47675Oct 21, 2024 · bpf: Fix use-after-free in bpf_uprobe_multi_link_attach()31Monitor
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 | 3213fdcab961026203dd587a4533600c70b3336b | Vendor (CNA) |
| Linux Linux | 35770ca6180caa24a2b258c99a87bd437a1ee10f | Vendor (CNA) |
| Linux Linux | 5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959 | Vendor (CNA) |
| Linux Linux | 65d0db500d7c07f0f76fc24a4d837791c4862cd2 | Vendor (CNA) |
| Linux Linux | 79a61cc3fc0466ad2b7b89618a6157785f0293b3 | Vendor (CNA) |
| Linux Linux | 954fd4c81f22c4b6ba65379a81fd252971bf4ef3 | Vendor (CNA) |
| Linux Linux | a95a24fcaee1b892e47d5e6dcc403f713874ee80 | Vendor (CNA) |
| azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 | 6.6.56.1-5 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 | 6.6.56.1-5 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.112-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-default | 3.0.101-108.168.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-ec2 | 3.0.101-108.168.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_47 | 17-150300.2.1 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_49 | 15-150300.2.1 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP4_Update_31 | 14-150400.2.1 · SUSE:Linux Enterprise Live Patching 15 SP4 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_0 | 21-150600.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_1 | 20-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-source | 3.0.101-108.168.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-syms | 3.0.101-108.168.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-trace | 3.0.101-108.168.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-xen | 3.0.101-108.168.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_60 | 15-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-37908217 days apartmm, slab: clean up slab->obj_exts always31Monitor
- CVE-2021-47110214 days apartx86/kvm: Disable kvmclock on all CPUs on shutdown28Monitor
- CVE-2024-476936 days apartIB/core: Fix ib_cache_setup_one error flow cleanup26Monitor
- CVE-2022-490126 days apartafs: Fix server->active leak in afs_put_server22Monitor
- CVE-2022-490286 days apartixgbevf: Fix resource leak in ixgbevf_init_module()22Monitor
- CVE-2024-477286 days apartbpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error22Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1699 · Oct 16, 2024(Linux Kernel Güvenlik Bildirimi)
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-459 · Incomplete CleanupCVSS 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/35770ca6180caa24a2b258c99a87bd437a1ee10f
- git.kernel.org/stable/c/5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959
- git.kernel.org/stable/c/65d0db500d7c07f0f76fc24a4d837791c4862cd2
- git.kernel.org/stable/c/79a61cc3fc0466ad2b7b89618a6157785f0293b3
- git.kernel.org/stable/c/954fd4c81f22c4b6ba65379a81fd252971bf4ef3
- git.kernel.org/stable/c/a95a24fcaee1b892e47d5e6dcc403f713874ee80
- project-zero.issues.chromium.org/issues/366053091
- 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.