Skip to main content
VulnerabilityPublished

CVE-2026-99643: Linux kernel · khugepaged: fix readahead lock inversion in collapse_file()

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99643· Medium

Not known to be exploited : upgrade to eadce52a9ef657d561b3e76c9b5f178bd99735f5 or b9b3c367faf1929fb8192a846b3604ad7eced008 when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in eadce52a9ef657d561b3e76c9b5f178bd99735f5, b9b3c367faf1929fb8192a846b3604ad7eced008

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to eadce52a9ef657d561b3e76c9b5f178bd99735f5 or b9b3c367faf1929fb8192a846b3604ad7eced008.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 730633f0b7f951726e87f912a6323641f674ae34, < eadce52a9ef657d561b3e76c9b5f178bd99735f5
Fixed in
  • eadce52a9ef657d561b3e76c9b5f178bd99735f5
LinuxLinuxAffected
  • ≥ 730633f0b7f951726e87f912a6323641f674ae34, < b9b3c367faf1929fb8192a846b3604ad7eced008
Fixed in
  • b9b3c367faf1929fb8192a846b3604ad7eced008
LinuxLinuxAffected
  • =5.15
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: khugepaged: fix readahead lock inversion in collapse_file() collapse_file() can call page_cache_sync_readahead() while still holding source folios locked. If truncate holds mapping->invalidate_lock exclusively and waits for one of those folios, readahead waits for invalidate_lock and neither side can make progress. We need to release those folio locks before starting readahead. On a page cache miss, roll back first, populate the collapse range, and retry once. Doing readahead after rollback avoids an extra pass when all folios are already present. If another miss occurs on retry, give up rather than keep retrying while truncate or reclaim removes folios. Keep page_cache_sync_readahead() and wait for read I/O with filemap_lock_folio(), releasing each folio before moving to the next. The existing uptodate check during collapse still handles read errors. Shmem uses shmem_get_folio() for swapin and fallocated folios without taking mapping->invalidate_lock, so it is unaffected.

References

Community reviews

Loading reviews…