Linux Kernel up to 6.6.152/6.12.104/6.18.45/7.1.9 s390-vfio_ccw _release_dev race condition

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 1.21- |
Summary
A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 6.6.152/6.12.104/6.18.45/7.1.9. Impacted is the function _release_dev of the component s390-vfio_ccw. This manipulation causes race condition.
This vulnerability is handled as CVE-2026-80553. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability has been found in Linux Kernel up to 6.6.152/6.12.104/6.18.45/7.1.9 and classified as very critical. Affected by this vulnerability is the function _release_dev of the component s390-vfio_ccw. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2026-80553 since 08/26/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/26/2026).
Upgrading to version 6.6.153, 6.12.105, 6.18.46 or 7.1.10 eliminates this vulnerability. Applying the patch e868ea8be0bc88c6982f48ecf3259d98afd884ae/dc47a98abe6714577a25224534dbd356051097a3/b7ae0f7993867d009a4b554fc1d6d451c10580a0/77f5e888d2e607a0b3141fb95091ad6ef1cca9a2/79c60b2c61105368dcc8444eb45847e21734f7c4 is able to eliminate this problem.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 6.6.152
- 6.12.104
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 6.18.45
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
- 7.1.5
- 7.1.6
- 7.1.7
- 7.1.8
- 7.1.9
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.5
VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.6.153/6.12.105/6.18.46/7.1.10
Patch: e868ea8be0bc88c6982f48ecf3259d98afd884ae/dc47a98abe6714577a25224534dbd356051097a3/b7ae0f7993867d009a4b554fc1d6d451c10580a0/77f5e888d2e607a0b3141fb95091ad6ef1cca9a2/79c60b2c61105368dcc8444eb45847e21734f7c4
Timeline
08/26/2026 Advisory disclosed08/26/2026 CVE reserved
08/26/2026 VulDB entry created
08/26/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-80553 (🔒)
GCVE (CVE): GCVE-0-2026-80553
GCVE (VulDB): GCVE-100-395851
Entry
Created: 08/26/2026 17:38Changes: 08/26/2026 17:38 (59)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.