Skip to main content
VulnerabilityPublished

CVE-2026-99731: Linux kernel · mm/filemap: don't lose a folio lock wakeup to a signal

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in da815f785e568accf0d4f2ec36233d316d5035c8 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 06:34 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in da815f785e568accf0d4f2ec36233d316d5035c8, 31cb998f208c078a6e9656b971bb311ea490ff1e, 8ccb6ded6a47b59b4907ed4f8c293cf8122de889 +2

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 to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.4.255 <5.5
Fixed in
  • da815f785e568accf0d4f2ec36233d316d5035c8
  • 31cb998f208c078a6e9656b971bb311ea490ff1e
  • 8ccb6ded6a47b59b4907ed4f8c293cf8122de889
  • 5.5
  • 3ce549d0df658a36602f2d03882688af0ea03faf
LinuxLinuxAffected
  • =5.9
Fixed in–

AI-suggested

A fix is available and has been applied in Linux kernel version 5.5 and specific commits listed in the established facts. Users and administrators should upgrade affected Linux kernel versions (>=5.4.255 <5.5 and =5.9) to version 5.5 or later to remediate this issue. No additional mitigation actions are indicated by the vendor advisory.

Description

CVE-2026-99731 is a Linux kernel vulnerability involving the memory management subsystem's folio lock wakeup mechanism. An exclusive waiter in folio_wait_bit_common() can prematurely exit the wait loop due to a fatal signal and be incorrectly woken by folio_unlock() without acquiring the lock. This causes folio_wake_bit() to stop after waking only the first waiter, potentially leaving other waiters asleep indefinitely on an unlocked folio. The issue has been fixed by allowing a waiter woken without a lock handoff to retry acquiring the lock, ensuring proper wakeup of subsequent waiters.

References

Community reviews

Loading reviews…