CVE Catalog

CVE-2026-53333

MediumCVSS 5.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.11%

2th percentile - higher than 2% of all known CVEs

Summary

In the Linux kernel mincore_swap() function, there is an ordering issue in entry checks. On builds without CONFIG_SWAP but with CONFIG_MIGRATION or CONFIG_MEMORY_FAILURE, migration/poison entries are incorrectly treated as swap, causing false warnings and incorrect results.

Risk Assessment

The organization may receive false WARN messages and incorrect memory page residency information, hindering diagnostics and potentially masking real issues.

Recommendation

Apply the patch that moves the CONFIG_SWAP check below the early return for non-swap entries.

Other vulnerabilities in Linux kernel

See all
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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS