CVE-2024-47674: Linux kernel · mm: avoid leaving partial pfn mappings around in error case
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 29 Oct 2026, 22:52 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
Description
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.
References
- nvd.nist.gov/vuln/detail/CVE-2024-47674 (opens in a new tab)
- git.kernel.org/stable/c/3213fdcab961026203dd587a4533600c70b3336b (opens in a new tab)
- git.kernel.org/stable/c/35770ca6180caa24a2b258c99a87bd437a1ee10f (opens in a new tab)
- git.kernel.org/stable/c/5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959 (opens in a new tab)
- git.kernel.org/stable/c/65d0db500d7c07f0f76fc24a4d837791c4862cd2 (opens in a new tab)
- git.kernel.org/stable/c/79a61cc3fc0466ad2b7b89618a6157785f0293b3 (opens in a new tab)
- git.kernel.org/stable/c/954fd4c81f22c4b6ba65379a81fd252971bf4ef3 (opens in a new tab)
- git.kernel.org/stable/c/a95a24fcaee1b892e47d5e6dcc403f713874ee80 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html (opens in a new tab)
- project-zero.issues.chromium.org/issues/366053091 (opens in a new tab)