Answer in brief
CVE-2026-89574 records a Unknown severity vulnerability in dm array: validate array block headers on read. 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 | >=6513c29f44f2cc970c0e9fecfe5a6526c3e73025 <67adda7ed5da3e3b64f5b9021a02c21fb374fd9c || >=6513c29f44f2cc970c0e9fecfe5a6526c3e73025 <b33f76d33aaeacf3baf3370d8d64985169b36600 || >=6513c29f44f2cc970c0e9fecfe5a6526c3e73025 <9808ddffb4bc659352df3020cd84d9d864820ee5 || >=6513c29f44f2cc970c0e9fecfe5a6526c3e73025 <2965787723084835b18dfe993cd450ebf5bd4540 | 67adda7ed5da3e3b64f5b9021a02c21fb374fd9c, b33f76d33aaeacf3baf3370d8d64985169b36600, 9808ddffb4bc659352df3020cd84d9d864820ee5, 2965787723084835b18dfe993cd450ebf5bd4540 |
| Linux/Linuxgeneric | 3.9 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: dm array: validate array block headers on read array_block_check() validates blocknr and csum and nothing else, while node_check(), next to it, has bounded the structural fields since both were written. dm_array_cursor_next() takes its loop bound from the on-disk nr_entries and element_at() is unguarded pointer arithmetic, so a count larger than the block holds keeps the cursor in one block while the index grows past it and the read walks off the dm-bufio buffer -- dm_cache_load_mappings() drives it once per cache block at activation. Check the header against itself: reject a zero value_size, require max_entries to equal calc_max_entries() for that value_size and block size, and require nr_entries to fit. Equality rather than an upper bound, since a count below the real capacity trips BUG_ON() in fill_ablock() and trim_ablock(). Metadata dm-array writes satisfies all three.
Quoted source text, attributed separately from HOL analysis.