Answer in brief
CVE-2026-80553 records a Unknown severity vulnerability in s390/vfio_ccw: Cancel existing workqueues. 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 | >=e5f84dbaea59b4f712dac428c337528b70e1c533 <e868ea8be0bc88c6982f48ecf3259d98afd884ae || >=e5f84dbaea59b4f712dac428c337528b70e1c533 <dc47a98abe6714577a25224534dbd356051097a3 || >=e5f84dbaea59b4f712dac428c337528b70e1c533 <b7ae0f7993867d009a4b554fc1d6d451c10580a0 || >=e5f84dbaea59b4f712dac428c337528b70e1c533 <77f5e888d2e607a0b3141fb95091ad6ef1cca9a2 || >=e5f84dbaea59b4f712dac428c337528b70e1c533 <79c60b2c61105368dcc8444eb45847e21734f7c4 | e868ea8be0bc88c6982f48ecf3259d98afd884ae, dc47a98abe6714577a25224534dbd356051097a3, b7ae0f7993867d009a4b554fc1d6d451c10580a0, 77f5e888d2e607a0b3141fb95091ad6ef1cca9a2, 79c60b2c61105368dcc8444eb45847e21734f7c4 |
| Linux/Linuxgeneric | 4.12 | Not reported |
Published upstream
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 26, 2026
In the Linux kernel, the following vulnerability has been resolved: s390/vfio_ccw: Cancel existing workqueues The initialization of the io_work and crw_work workqueues begs the question of whether they should be un-initialized. Add the corresponding cleanup tags in _release_dev to ensure work isn't dispatched after the private struct is free'd.
Quoted source text, attributed separately from HOL analysis.