CVE-2026-99136

LOWCVSS 7.0 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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.

0.0/ 10 priority

Sources & remediation

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-10-31: 110-31
Referenced assets1 URL
Full discourse1 post
  • cve.now@cvedotnow

    🔴 Linux kernel: race condition in dm-crypt lets failed I/O report success (CVE-2026-99136) A local user may be able to time I/O so that failed encrypted disk reads or writes are reported as successful. Disclosed Oct 28 Patch → 2.6.29, 5.10.273 and more https://cve.now/CVE-2026-99136?utm_source=x&utm_medium=social&utm_campaign=cvedotnow&utm_content=critical

    000001.2K
    19.6K followersView on X

Explore more