Answer in brief
CVE-2024-47674 records a Unknown severity vulnerability in mm: avoid leaving partial pfn mappings around in error case. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-47674 records a Unknown severity vulnerability in mm: avoid leaving partial pfn mappings around in error case. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b97a50adb37e98b940a30c4656565ff609aa8f94 <3213fdcab961026203dd587a4533600c70b3336b || >=69d4e1ce9087c8767f2fe9b9426fa2755c8e9072 <35770ca6180caa24a2b258c99a87bd437a1ee10f || >=74ffa5a3e68504dd289135b1cf0422c19ffb3f2e <5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959 || >=74ffa5a3e68504dd289135b1cf0422c19ffb3f2e <65d0db500d7c07f0f76fc24a4d837791c4862cd2 || >=74ffa5a3e68504dd289135b1cf0422c19ffb3f2e <a95a24fcaee1b892e47d5e6dcc403f713874ee80 || >=74ffa5a3e68504dd289135b1cf0422c19ffb3f2e <954fd4c81f22c4b6ba65379a81fd252971bf4ef3 || >=74ffa5a3e68504dd289135b1cf0422c19ffb3f2e <79a61cc3fc0466ad2b7b89618a6157785f0293b3 | 3213fdcab961026203dd587a4533600c70b3336b, 35770ca6180caa24a2b258c99a87bd437a1ee10f, 5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959, 65d0db500d7c07f0f76fc24a4d837791c4862cd2, a95a24fcaee1b892e47d5e6dcc403f713874ee80, 954fd4c81f22c4b6ba65379a81fd252971bf4ef3, 79a61cc3fc0466ad2b7b89618a6157785f0293b3 |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
Oct 15, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b97a50adb37e98b940a30c4656565ff609aa8f94 <3213fdcab961026203dd587a4533600c70b3336b || >=69d4e1ce9087c8767f2fe9b9426fa2755c8e9072 <35770ca6180caa24a2b258c99a87bd437a1ee10f || >=74ffa5a3e68504dd289135b1cf0422c19ffb3f2e <5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959 || >=74ffa5a3e68504dd289135b1cf0422c19ffb3f2e <65d0db500d7c07f0f76fc24a4d837791c4862cd2 || >=74ffa5a3e68504dd289135b1cf0422c19ffb3f2e <a95a24fcaee1b892e47d5e6dcc403f713874ee80 || >=74ffa5a3e68504dd289135b1cf0422c19ffb3f2e <954fd4c81f22c4b6ba65379a81fd252971bf4ef3 || >=74ffa5a3e68504dd289135b1cf0422c19ffb3f2e <79a61cc3fc0466ad2b7b89618a6157785f0293b3 | 3213fdcab961026203dd587a4533600c70b3336b, 35770ca6180caa24a2b258c99a87bd437a1ee10f, 5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959, 65d0db500d7c07f0f76fc24a4d837791c4862cd2, a95a24fcaee1b892e47d5e6dcc403f713874ee80, 954fd4c81f22c4b6ba65379a81fd252971bf4ef3, 79a61cc3fc0466ad2b7b89618a6157785f0293b3 |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
Oct 15, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.