Answer in brief
CVE-2026-80710 records a High severity (CVSS 7.8) vulnerability in s390/dasd: Fix undersized format-check buffer. 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.
CVSS is 7.8. 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 | >=8fd575200db5b53f6ea6818dd017f1b43190db12 <aca18289c86f22d3fc2f3f6ff615286e7b1702f6 || >=8fd575200db5b53f6ea6818dd017f1b43190db12 <9f88dda2f22927d22498801a92cab6a9424eaf86 || >=8fd575200db5b53f6ea6818dd017f1b43190db12 <e16e0fc54120cee3c6f0362de95aab6792865857 || >=8fd575200db5b53f6ea6818dd017f1b43190db12 <87f3389cd3920714c53e704778f7ca7f1cf0c39c || >=8fd575200db5b53f6ea6818dd017f1b43190db12 <7f40b346462f563a0d6e841a77b5163d2a882a04 | aca18289c86f22d3fc2f3f6ff615286e7b1702f6, 9f88dda2f22927d22498801a92cab6a9424eaf86, e16e0fc54120cee3c6f0362de95aab6792865857, 87f3389cd3920714c53e704778f7ca7f1cf0c39c, 7f40b346462f563a0d6e841a77b5163d2a882a04 |
| Linux/Linuxgeneric | 4.7 | Not reported |
Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 28, 2026
In the Linux kernel, the following vulnerability has been resolved: s390/dasd: Fix undersized format-check buffer fmt_buffer_size in dasd_eckd_check_device_format() is declared as int, even though one of the multiplicands, sizeof(struct eckd_count), is a size_t. The expression trkcount * rpt_max * sizeof(struct eckd_count) is therefore correctly evaluated at 64-bit width, but the result is silently truncated when it is stored back into the 32-bit fmt_buffer_size variable. For a sufficiently large track range (start_unit/stop_unit are caller-controlled) this truncation yields a buffer size far smaller than the number of tracks actually requested. kzalloc() then succeeds with an undersized allocation, while the subsequent channel program build still operates on the untruncated track count and writes past the end of that buffer. Compute the buffer size with check_mul_overflow() and keep it in a size_t, so that a value that no longer fits results in -EINVAL instead of a silently truncated allocation size.
Quoted source text, attributed separately from HOL analysis.