mm/memfd_luo: fix physical address conversion in put_folios cleanup
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3538f90ab89aaf302782b4b073a0aae66904cd67 and Kernel bd0d6bde286a2b8e3ae7975b0dcc2d43875d5fc9.
In the Linux kernel, the following vulnerability has been resolved: mm/memfd_luo: fix physical address conversion in put_folios cleanup In memfd_luo_retrieve_folios()'s put_folios cleanup path: 1. kho_restore_folio() expects a phys_addr_t (physical address) but receives a raw PFN (pfolio->pfn). This causes kho_restore_page() to check the wrong physical address (pfn << PAGE_SHIFT instead of the actual physical address). 2. This loop lacks the !pfolio->pfn check that exists in the main retrieval loop and memfd_luo_discard_folios(), which could incorrectly process sparse file holes where pfn=0. Fix by converting PFN to physical address with PFN_PHYS() and adding the !pfolio->pfn check, matching the pattern used elsewhere in this file. This issue was identified by the AI review. https://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.19, >=b3749f174d686627f702234e64bad976dc432dbc <3538f90ab89aaf302782b4b073a0aae66904cd67, >=b3749f174d686627f702234e64bad976dc432dbc <bd0d6bde286a2b8e3ae7975b0dcc2d43875d5fc9 | 3538f90ab89aaf302782b4b073a0aae66904cd67, bd0d6bde286a2b8e3ae7975b0dcc2d43875d5fc9 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket