CVE-2024-27007: userfaultfd: change src_folio after ensuring it's unpinned in UFFDIO_MOVE
In the Linux kernel, the following vulnerability has been resolved:
userfaultfd: change src_folio after ensuring it's unpinned in UFFDIO_MOVE
Commit d7a08838ab74 ("mm: userfaultfd: fix unexpected change to src_folio
when UFFDIO_MOVE fails") moved the src_folio->{mapping, index} changing to
after clearing the page-table and ensuring that it's not pinned. This
avoids failure of swapout+migration and possibly memory corruption.
However, the commit missed fixing it in the huge-page case.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux userfaultfd memory movement can cause failed memory operations and possible memory corruption in the huge-page path. The supplied CVSS rates it 7.8: exploitation requires a low-privilege local account, not remote network access, but successful abuse could seriously affect confidentiality, integrity, and availability.
Executive priority
Treat this as an expedited kernel-patching issue, particularly on multi-user or shared-compute hosts. Its potential impact is high, but the local access requirement and absence of cited exploitation evidence do not support an internet-wide emergency response. Require asset owners to confirm running-kernel remediation rather than merely reporting that an update was installed.
Technical view
The huge-page branch of UFFDIO_MOVE did not receive an earlier correction that delays changing src_folio mapping and index until page-table clearing confirms the folio is unpinned. Consequently, swapout or migration can fail and memory corruption may be possible. The cited Linux stable commits provide the source-level corrections.
Likely exposure
The bundle identifies affected Linux 6.8 and 6.9 release ranges, with a 6.8.8 boundary, but does not establish every distribution's backport status. Risk is greatest where low-privilege local users can reach UFFDIO_MOVE and its huge-page path. Internet exposure alone does not enable exploitation under the supplied local-attack CVSS vector.
Exploitation context
The supplied sources provide no evidence of active exploitation, and this CVE is not marked as CISA KEV. They also do not identify a public proof of concept. Exploitation would require local, low-privilege access and interaction with the vulnerable memory-management path; practical reliability and privilege-escalation outcomes are not established by the bundle.
Researcher notes
The key defect is the huge-page case omitted from an earlier UFFDIO_MOVE correction. The record supports possible memory corruption and swapout or migration failure, but does not document exploit mechanics, demonstrated privilege escalation, or affected configuration prerequisites. Assess exact exposure through source ancestry and distribution backports using the two cited stable commits.
Mitigation direction
Inventory active Linux kernel versions and obtain each distribution's CVE-2024-27007 status.
Apply a vendor kernel update incorporating the applicable cited Linux stable fix.
Reboot systems into the corrected kernel after following normal change controls.
If no update is available, request vendor guidance; the sources name no workaround.
Prioritize multi-user and shared-compute systems permitting untrusted local accounts.
Validation and detection
Confirm the running kernel version, not only the installed package version.
Verify the active kernel contains the applicable stable fix or equivalent vendor backport.
Review vendor advisories because distribution version numbers may not match upstream ranges.
Confirm systems restarted successfully into the corrected kernel.
Re-scan affected assets and investigate any remaining findings against vendor backport evidence.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-27007 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.