Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99136

dm-crypt: fix a tiny race condition in crypt_dec_pending

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.

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 3 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-99136, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.

Affected products

  • Linux · Linux

    • affected b35f8caa0890169000fec22902290d9a15274cbd – < 445a6883f46d3ab1ff545199a8cc1d5834936d3f
    • affected b35f8caa0890169000fec22902290d9a15274cbd – < 6f82e86471c92fd874f2630c9a6af887f4ed1a77
    • affected b35f8caa0890169000fec22902290d9a15274cbd – < 6ac8546df1f8a2b1ca7f6d67c269057a99fbbf8c
    • affected b35f8caa0890169000fec22902290d9a15274cbd – < 056bf8322e39a48026df352d6227ec03dd8cd032
    • affected b35f8caa0890169000fec22902290d9a15274cbd – < d9d7069bb79139271b54dc477f07e242c445de6b
    • affected b35f8caa0890169000fec22902290d9a15274cbd – < ac5d887ab93592fc5e3605fe30c1d8d232d609b3
    • affected b35f8caa0890169000fec22902290d9a15274cbd – < 4f16bb982b27b9f5a15301f622c318001fe521f8
    • affected b35f8caa0890169000fec22902290d9a15274cbd – < 148845aa1921d95ef5dc851c76e6a284f6657df6
    • affected 9c8f3fcd3ffd3283cc0971c8919058356f20a963
    • affected 2.6.28.9 – < 2.6.29
  • Linux · Linux

    • affected 2.6.29
    • unaffected < 2.6.29
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.59 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99136 badge
[![CVE-2026-99136](https://cveledger.app/badge/CVE-2026-99136.svg)](https://cveledger.app/cve/CVE-2026-99136)

Record last updated .