Answer in brief
CVE-2026-90052 records a Unknown severity vulnerability in dm-integrity: fix buffer overflow with keyed discard. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5c58ea19a909ef6bed4f0f824e9cd7e30d7e4775 <9988c1c9e0d1c78391e3d8e2817beb667470c76f || >=6228722c27304e4682cddc1fede03898f87e4414 <dd08a645195f410f2dcaa40de379a45ce110e873 || >=68c5c42567bc462139128968ebbfadd0aefff519 <59e6f919d77d72ec79cbf171256f2f7819737580 | 9988c1c9e0d1c78391e3d8e2817beb667470c76f, dd08a645195f410f2dcaa40de379a45ce110e873, 59e6f919d77d72ec79cbf171256f2f7819737580 |
| Linux/Linuxgeneric | 7.3-rc1 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix buffer overflow with keyed discard Since commit 68c5c42567bc ("dm-integrity: replace forgeable discard filler with a keyed sector marker"), integrity_metadata computes a checksum for every discarded block into the "checksums" buffer. integrity_sector_checksum always writes the whole digest. So if the tag size is smaller than the digest size, the checksum of the last block that fits into the buffer is written past the end of it. For example, with hmac(sha256) and tag size 16, a 4MiB discard writes 16 bytes past the kmalloc'ed page. Fix this by subtracting extra_space from the buffer size when computing max_blocks, like we do for writes.
Quoted source text, attributed separately from HOL analysis.