CVE-2026-53333: mm/mincore: handle non-swap entries before !CONFIG_SWAP guard

Published Jul 1, 2026

Updated

In the Linux kernel, the following vulnerability has been resolved:

mm/mincore: handle non-swap entries before !CONFIGSWAP guard

mincoreswap() also fields migration/hwpoison entries (and shmem swapin-error entries), which can exist on !CONFIGSWAP builds when CONFIGMIGRATION or CONFIGMEMORYFAILURE is enabled. The !ISENABLED(CONFIGSWAP) guard ran before the non-swap-entry early return, so mincorepterange() can spuriously WARN and report these pages nonresident on !CONFIGSWAP 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 Software

1 affected component

Linux Kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Configuration
Patch the kernel mm/mincore logic so that the !CONFIG_SWAP guard runs after the non-swap-entry check (handle non-swap entries before !CONFIG_SWAP), preventing spurious WARNs for migration/hwpoison/shmem-related entries on !CONFIG_SWAP builds.
Linux kernel (mm/mincore) Guard position for CONFIG_SWAP check in mincore_swap/mincore_pte_range = Move the guard below the non-swap-entry early return so only true swap entries are handled

Event History

Jul 1, 2026

CVE Published

via MITRE·01:32 PM

Data Sourced

via MITRE·01:32 PM

Description

Data Sourced

via NVD·02:16 PM

Description

Frequently Asked Questions

Which systems are affected by this issue?

Linux kernel builds with CONFIG_SWAP disabled can be affected when CONFIG_MIGRATION or CONFIG_MEMORY_FAILURE is enabled, because migration or hardware-poison entries may still be present.

What conditions trigger the incorrect behavior?

The issue occurs when mincore processes migration, hwpoison, or shmem swapin-error entries on a kernel built without swap support. The affected path can emit a spurious WARN and report pages as nonresident.

Does exploitation require an attacker to create or use actual swap entries?

No. The problematic entries are non-swap entries, including migration and hwpoison entries, that can exist even on builds where CONFIG_SWAP is disabled.

What is the impact on mincore results?

Affected kernels can incorrectly report the relevant pages as nonresident. They may also generate a WARN despite the entries not being true swap entries.

CVE-2026-53333: mm/mincore: handle non-swap entries before !CONFIG_SWAP guard

Affected Software

Remediation

Event History

Frequently Asked Questions

Which systems are affected by this issue?

What conditions trigger the incorrect behavior?

Does exploitation require an attacker to create or use actual swap entries?

What is the impact on mincore results?

Company

Resources

Contact

Frequently Asked Questions

Which systems are affected by this issue?

What conditions trigger the incorrect behavior?

Does exploitation require an attacker to create or use actual swap entries?

What is the impact on mincore results?