CVE-2026-53333
UnknownSummary
In the Linux kernel, the mincore_swap() function incorrectly checked the !CONFIG_SWAP guard before handling non-swap entries (migration, hwpoison, shmem swapin-error). This caused spurious WARN messages and incorrect reporting of pages as non-resident on !CONFIG_SWAP kernels with CONFIG_MIGRATION or CONFIG_MEMORY_FAILURE enabled.
Risk Assessment
Organizations may receive misleading page residency information, complicating memory diagnostics and potentially leading to incorrect operational decisions. False WARN messages can also mask real system issues.
Recommendation
Immediately update the Linux kernel to a version containing the fix that moves the !CONFIG_SWAP guard below the non-swap entry handling. This is critical for systems with migration or memory failure support but without swap enabled.
Original NVD description (English source)
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.