mm/mincore: handle non-swap entries before !CONFIG_SWAP guard
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.367.0.137.1In 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.
From the CVE record · Linux
On Linux kernels built without CONFIG_SWAP but with CONFIG_MIGRATION or CONFIG_MEMORY_FAILURE, mincore can spuriously warn and report migration or hardware-poisoned pages as nonresident. The input does not describe an attacker action, authentication requirement, or user-interaction requirement.
Check Linux kernel builds without CONFIG_SWAP that enable CONFIG_MIGRATION or CONFIG_MEMORY_FAILURE; affected versions are not specified.