mm/mincore: handle non-swap entries before !CONFIG_SWAP guard
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0c25b8734367574e21aeb8468c2e522713134da7, Kernel 3481d4372ae34243f7025925314385b852c50f7e and Kernel a8f91ddf67f669f547bb9fb559738da6f8ee2cf3.
In the Linux kernel, the following vulnerability has been resolved: mm/mincore: handle non-swap entries before !CONFIG_SWAP guard mincore_swap() also fields migration/hwpoison entries (and shmem swapin-error entries), which can exist on !CONFIG_SWAP builds when CONFIG_MIGRATION or CONFIG_MEMORY_FAILURE is enabled. The !IS_ENABLED(CONFIG_SWAP) guard ran before the non-swap-entry early return, so mincore_pte_range() can spuriously WARN and report these pages nonresident on !CONFIG_SWAP kernels. Move the guard below the non-swap-entry check so only true swap entries trip the WARN, and migration/hwpoison entries take the existing "uptodate / non-shmem" path.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.18, >=1f2052755c152940c336918bd73d13d5468f548b <0c25b8734367574e21aeb8468c2e522713134da7, >=1f2052755c152940c336918bd73d13d5468f548b <3481d4372ae34243f7025925314385b852c50f7e, >=1f2052755c152940c336918bd73d13d5468f548b <a8f91ddf67f669f547bb9fb559738da6f8ee2cf3 | 0c25b8734367574e21aeb8468c2e522713134da7, 3481d4372ae34243f7025925314385b852c50f7e, a8f91ddf67f669f547bb9fb559738da6f8ee2cf3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket