VulnerabilityPublished 28 Oct 2026

CVE-2026-99136: Linux kernel · dm-crypt: fix a tiny race condition in crypt_dec_pending

Affects Linux kernelSource CVE Database V5

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

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in ac5d887ab93592fc5e3605fe30c1d8d232d609b3, 148845aa1921d95ef5dc851c76e6a284f6657df6, 4f16bb982b27b9f5a15301f622c318001fe521f8 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to ac5d887ab93592fc5e3605fe30c1d8d232d609b3, 148845aa1921d95ef5dc851c76e6a284f6657df6, 4f16bb982b27b9f5a15301f622c318001fe521f8 or 2.6.29.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=2.6.28.9 <2.6.29	Fixed in ac5d887ab93592fc5e3605fe30c1d8d232d609b3 148845aa1921d95ef5dc851c76e6a284f6657df6 4f16bb982b27b9f5a15301f622c318001fe521f8 2.6.29
LinuxLinux	Affected =2.6.29	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: dm-crypt: fix a tiny race condition in crypt_dec_pending crypt_dec_pending reads io->error before calling atomic_dec_and_test. Another context, for example crypt_endio called from an interrupt, may set io->error and drop its reference between the read and the decrement. crypt_dec_pending then drops the last reference and completes the bio with the stale status - so a read that failed and was never decrypted, or a write that failed, is reported as successful. The read was placed before the decrement by commit b35f8caa0890 ("dm crypt: wait for endio to complete before destruction"), because that commit freed dm_crypt_io before calling bio_endio. This is no longer the case, dm_crypt_io lives in the per-bio data now. Read io->error after atomic_dec_and_test instead. atomic_dec_and_test is fully ordered, so no additional barrier is needed.

References

Community reviews

Loading reviews…