Bug 2577764 (CVE-2026-99668)

Summary: CVE-2026-99668 kernel: kernel: Denial of Service via improper handling of device-private THP migration entries
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: akhatavk, aos-team-art-private, asdas, dpaolell, jdelft, jupierce, lgarciaa, mbiarnes, ppalepu, ppostler, prdhamdh, rhel-process-autobot, sghai, sidsharm, suppawar, vlaad, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Linux kernel's memory management subsystem. A local attacker could cause a Denial of Service (DoS) or kernel memory corruption due to improper validation of device-private Transparent Huge Page (THP) migration entries. When clearing page table entries, the kernel inspects the underlying memory folio type rather than the entry type, mistakenly treating a migration entry as an active device-private entry. A local user can trigger this issue by issuing concurrent memory advice operations while memory is migrating back to system memory, causing the kernel to drop reference counts repeatedly and crash.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-11-20 06:12:36 UTC
In the Linux kernel, the following vulnerability has been resolved:

mm/huge_memory: fix zapping migration entries for device-private THPs

A PMD migration entry can refer to a device-private folio.
zap_huge_pmd_folio() checks the folio type instead of the entry type,
so it treats such a migration entry as a device-private entry.

Installing the migration entry already removed the reverse mapping and
dropped the mapping reference. Zapping it must not repeat those
operations. Concurrent MADV_DONTNEED during migration back to system
memory can trigger this.

Check the PMD entry type using pmd_is_device_private_entry().

Fix generated by an LLM and sent by Chris Mason in private.

[ david: simplify description ]