Discard hang via zero-progress metadata loop
Published Oct 28, 2026 · Updated Oct 28, 2026
An infinite loop in Linux dm-integrity allows local users to hang discard processing through requests to an affected block device. In integrity_metadata, allocation failure selects a stack buffer but sizes batches using HASH_MAX_DIGESTSIZE, producing zero blocks per iteration when tags exceed that size. Triggering requires discard support, oversized tags, allocation failure, and access to submit discards; the request never completes and a kernel worker spins.
Summary
What happened
An infinite loop in Linux dm-integrity allows local users to hang discard processing through requests to an affected block device. In integrity_metadata, allocation failure selects a stack buffer but sizes batches using HASH_MAX_DIGESTSIZE, producing zero blocks per iteration when tags exceed that size. Triggering requires discard support, oversized tags, allocation failure, and access to submit discards; the request never completes and a kernel worker spins.
The record
- CVE
- CVE-2026-99135
- Published
- Oct 28, 2026
- Updated
- Oct 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 28, 2026CVE publishedPublication date reported by the CVE source.
- Oct 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.7
- Affected versionversion=84597a44a9d86ac949900441cea7da0af0f2f473 <18d80c77b4c7dd20699e81cedfbbff4e9d198f28
- Affected versionversion=84597a44a9d86ac949900441cea7da0af0f2f473 <251b44b424920df9204e88a81fb3f78fa48ddd99
- Affected versionversion=84597a44a9d86ac949900441cea7da0af0f2f473 <fc512700f1413fed652dac22fa1c4e837210b9c0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us