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-99135dm-integrity: fix infinite loop on discard with large tag size

Description

In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix infinite loop on discard with large tag size When integrity_metadata handles a discard, it fills a buffer with DISCARD_FILLER and writes it over the tags, max_blocks blocks at a time. If the kmalloc fails, the buffer is the on-stack array checksums_onstack and max_size is set to HASH_MAX_DIGESTSIZE. So if the tag size is larger than HASH_MAX_DIGESTSIZE, max_blocks is zero, bi_size is never decremented and the loop never terminates. Fix this by using sizeof(checksums_onstack) as max_size. The array has MAX_TAG_SIZE bytes since commit b93b6643e9b5 ("dm integrity: fix a crash with unusually large tag size"), so max_blocks is at least 1.

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 2 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 84597a44a9d86ac949900441cea7da0af0f2f473 – < f41a224b3c9d66c7b59afc7cae02a8b214f3c684
    • affected 84597a44a9d86ac949900441cea7da0af0f2f473 – < c66f5c6ccfa832d28b44a66c01e3468c246adac4
    • affected 84597a44a9d86ac949900441cea7da0af0f2f473 – < 41a18e6c6e2c4a912494a035c17ecfe79c68b9e6
    • affected 84597a44a9d86ac949900441cea7da0af0f2f473 – < bbc154a7da4e075aef720ef051aff6094400eb66
    • affected 84597a44a9d86ac949900441cea7da0af0f2f473 – < c4cba6670fa199415689f67108e96b0ba469d767
    • affected 84597a44a9d86ac949900441cea7da0af0f2f473 – < fc512700f1413fed652dac22fa1c4e837210b9c0
    • affected 84597a44a9d86ac949900441cea7da0af0f2f473 – < 251b44b424920df9204e88a81fb3f78fa48ddd99
    • affected 84597a44a9d86ac949900441cea7da0af0f2f473 – < 18d80c77b4c7dd20699e81cedfbbff4e9d198f28
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • 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-99135 badge
[![CVE-2026-99135](https://cveledger.app/badge/CVE-2026-99135.svg)](https://cveledger.app/cve/CVE-2026-99135)

Record last updated .