CVE-2026-99135 json
dm-integrity: fix infinite loop on discard with large tag size
published 14d ago modified 12d ago also EUVD-2026-111887
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.115-2
- linux Debian 14 7.2.13-1
debian advisories DEBIAN-CVE-2026-99135
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-111254
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/f41a224b3c9d66c7b59afc7cae02a8b214f3c684 commit
- git.kernel.org/stable/c/c66f5c6ccfa832d28b44a66c01e3468c246adac4 commit
- git.kernel.org/stable/c/41a18e6c6e2c4a912494a035c17ecfe79c68b9e6 commit
- git.kernel.org/stable/c/bbc154a7da4e075aef720ef051aff6094400eb66 commit
- git.kernel.org/stable/c/c4cba6670fa199415689f67108e96b0ba469d767 commit
- git.kernel.org/stable/c/fc512700f1413fed652dac22fa1c4e837210b9c0 commit
- git.kernel.org/stable/c/251b44b424920df9204e88a81fb3f78fa48ddd99 commit
- git.kernel.org/stable/c/18d80c77b4c7dd20699e81cedfbbff4e9d198f28 commit
Is CVE-2026-99135 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99135 updated cvss 4.7
kernel: kernel: Denial of Service via infinite loop in dm-integrity discard handling
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/f41a224b3c9d66c7b59afc7cae02a8b214f3c684
- git.kernel.org /stable/c/c66f5c6ccfa832d28b44a66c01e3468c246adac4
- git.kernel.org /stable/c/41a18e6c6e2c4a912494a035c17ecfe79c68b9e6
- git.kernel.org /stable/c/bbc154a7da4e075aef720ef051aff6094400eb66
- git.kernel.org /stable/c/c4cba6670fa199415689f67108e96b0ba469d767
- git.kernel.org /stable/c/fc512700f1413fed652dac22fa1c4e837210b9c0
- git.kernel.org /stable/c/251b44b424920df9204e88a81fb3f78fa48ddd99
- git.kernel.org /stable/c/18d80c77b4c7dd20699e81cedfbbff4e9d198f28
Sources
- CVE List CVE-2026-99135
- NVD CVE-2026-99135
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.