CVE-2026-80547
Received Received - Intake

s390/vfio_ccw CRW Lock Implementation for Asynchronous Events

Publication date: 2026-08-26

Last updated on: 2026-08-26

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: s390/vfio_ccw: Implement a crw lock Unlike the channel_program struct, which covers synchronous I/O submissions and asynchronous interrupts, the CRW region relies exclusively on asynchronous events coming from hardware. Implement a lock to manage the list of those payloads, to ensure they are read cohesively.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-26
Last Modified
2026-08-26
Generated
2026-08-26
AI Q&A
2026-08-26
EPSS Evaluated
N/A
NVD
CVE-2026-80547
EUVD
EUVD-2026-66462

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a missing lock mechanism for the CRW region in the s390/vfio_ccw driver. The CRW region handles asynchronous hardware events, and without a proper lock, concurrent access could lead to inconsistent data reads from payloads.

Impact Analysis

This vulnerability could cause data corruption or crashes in systems using the s390/vfio_ccw driver, particularly on IBM Z (s390x) architectures. It may lead to unreliable hardware event handling, affecting virtualization or I/O operations.

Mitigation Strategies

Update the Linux kernel to a patched version that includes the s390/vfio_ccw crw lock implementation to resolve the vulnerability.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-80547. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart