VulnerabilityPublished 28 Oct 2026

CVE-2026-99135: Linux kernel · dm-integrity: fix infinite loop on discard with large tag size

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in fc512700f1413fed652dac22fa1c4e837210b9c0 : 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 fc512700f1413fed652dac22fa1c4e837210b9c0, 251b44b424920df9204e88a81fb3f78fa48ddd99, 18d80c77b4c7dd20699e81cedfbbff4e9d198f28

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 fc512700f1413fed652dac22fa1c4e837210b9c0, 251b44b424920df9204e88a81fb3f78fa48ddd99 or 18d80c77b4c7dd20699e81cedfbbff4e9d198f28.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 84597a44a9d86ac949900441cea7da0af0f2f473, < fc512700f1413fed652dac22fa1c4e837210b9c0	Fixed in fc512700f1413fed652dac22fa1c4e837210b9c0
LinuxLinux	Affected ≥ 84597a44a9d86ac949900441cea7da0af0f2f473, < 251b44b424920df9204e88a81fb3f78fa48ddd99	Fixed in 251b44b424920df9204e88a81fb3f78fa48ddd99
LinuxLinux	Affected ≥ 84597a44a9d86ac949900441cea7da0af0f2f473, < 18d80c77b4c7dd20699e81cedfbbff4e9d198f28	Fixed in 18d80c77b4c7dd20699e81cedfbbff4e9d198f28
LinuxLinux	Affected =5.7	Fixed in–

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.

References

Community reviews

Loading reviews…