s390/vfio_ccw: Move cp cleanup out of not operational (CVE-2026-80549) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80549

s390/vfio_ccw: Move cp cleanup out of not operational

Answer in brief

CVE-2026-80549 records a Unknown severity vulnerability in s390/vfio_ccw: Move cp cleanup out of not operational. 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.

Published Aug 26, 2026Updated Aug 26, 2026Source checked Aug 26, 2026First seen by HOL Aug 26, 2026Material review Aug 26, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=204b394a23ad5e30944f23518e21e844614da2ff <f98a9890ca42f4223d2d4c50e0660af3e012fcb4 \|\| >=204b394a23ad5e30944f23518e21e844614da2ff <4e3301e2a651d742c05914f6074a25b8e41bce19 \|\| >=204b394a23ad5e30944f23518e21e844614da2ff <af1759d8e6e6da9ba94f30a2f92546f406899aa7 \|\| >=204b394a23ad5e30944f23518e21e844614da2ff <56100baa0eb7055b1026dfa73e696e8066ff71fd \|\| >=204b394a23ad5e30944f23518e21e844614da2ff <0c11f61a876ed6fcca53d442ed3f33ea8362a0f9	f98a9890ca42f4223d2d4c50e0660af3e012fcb4, 4e3301e2a651d742c05914f6074a25b8e41bce19, af1759d8e6e6da9ba94f30a2f92546f406899aa7, 56100baa0eb7055b1026dfa73e696e8066ff71fd, 0c11f61a876ed6fcca53d442ed3f33ea8362a0f9
Linux/Linuxgeneric	6.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to f98a9890ca42f4223d2d4c50e0660af3e012fcb4 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 26, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: s390/vfio_ccw: Move cp cleanup out of not operational The fsm_notoper() routine is called when the device has been lost, and is (by definition) no longer operational. Since this can happen asynchronously from the normal behavior of the driver, the cleanup may happen when holding other locks in the calling sequence (notably, the cio subchannel lock). Push the cleanup of the private->cp resources to a workqueue, where it can be done out from under that lock sequence and a future patch can safely manage the locking requirements.

Quoted source text, attributed separately from HOL analysis.