Hang via lost folio-lock wakeup
Published Nov 20, 2026 · Updated Nov 20, 2026
A lost-wakeup race in Linux filemap allows attackers to hang folio waiters via a fatal signal racing with a lock release. In mm/filemap.c, folio_wait_bit_common() returns -EINTR without acquiring an available lock after an exclusive waiter receives a wakeup without lock handoff, preventing propagation to remaining waiters. The race requires precisely timed signal delivery and concurrent folio contention; the documented consequence is indefinitely sleeping waiters, not a demonstrated system-wide crash.
Summary
What happened
A lost-wakeup race in Linux filemap allows attackers to hang folio waiters via a fatal signal racing with a lock release. In mm/filemap.c, folio_wait_bit_common() returns -EINTR without acquiring an available lock after an exclusive waiter receives a wakeup without lock handoff, preventing propagation to remaining waiters. The race requires precisely timed signal delivery and concurrent folio contention; the documented consequence is indefinitely sleeping waiters, not a demonstrated system-wide crash.
The record
- CVE
- CVE-2026-99731
- Published
- Nov 20, 2026
- Updated
- Nov 20, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 20, 2026CVE publishedPublication date reported by the CVE source.
- Nov 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.4.255 <5.5
- Affected versionversion=5.9
- Affected versionversion=5ef64cc8987a9211d3f3667331ba3411a94ddc79 <31cb998f208c078a6e9656b971bb311ea490ff1e
- Affected versionversion=5ef64cc8987a9211d3f3667331ba3411a94ddc79 <3ce549d0df658a36602f2d03882688af0ea03faf
- Affected versionversion=5ef64cc8987a9211d3f3667331ba3411a94ddc79 <8ccb6ded6a47b59b4907ed4f8c293cf8122de889
- Affected versionversion=5ef64cc8987a9211d3f3667331ba3411a94ddc79 <da815f785e568accf0d4f2ec36233d316d5035c8
- Affected versionversion=c404e1e19780d8977f67411a3b951a964c6361ae
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- Folio lost-wakeup kernel regression reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us