Kernel panic via unlocked DASD queue traversal
Published May 21, 2024 · Updated May 11, 2026
Race condition in the Linux kernel s390 DASD driver 3.1 through 6.7-rc2 allows local users to trigger a kernel panic via parallel I/O. The dasd_profile_start() function walks and counts a mutable device request queue without holding its device lock, so concurrent queue changes cause invalid pointer accesses. Reaching the crash requires local low-privileged access and heavy parallel DASD I/O, with alias devices increasing exposure.
Summary
What happened
Race condition in the Linux kernel s390 DASD driver 3.1 through 6.7-rc2 allows local users to trigger a kernel panic via parallel I/O. The dasd_profile_start() function walks and counts a mutable device request queue without holding its device lock, so concurrent queue changes cause invalid pointer accesses. Reaching the crash requires local low-privileged access and heavy parallel DASD I/O, with alias devices increasing exposure.
The record
- CVE
- CVE-2023-52774
- Published
- May 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.1
- Affected versionversion=4fa52aa7a82f9226b3874a69816bda3af821f002 <6062c527d0403cef27c54b91ac8390c3a497b250
- Affected versionversion=4fa52aa7a82f9226b3874a69816bda3af821f002 <9372aab5d0ff621ea203c8c603e7e5f75e888240
- Affected versionversion=4fa52aa7a82f9226b3874a69816bda3af821f002 <c841de6247e94e07566d57163d3c0d8b29278f7a
- Affected versionversion=4fa52aa7a82f9226b3874a69816bda3af821f002 <db46cd1e0426f52999d50fa72cfa97fa39952885
- Affected versionversion=4fa52aa7a82f9226b3874a69816bda3af821f002 <dc96fde8fcb2b896fd6c64802a7f4ece2e69b0be
- Affected versionversion=4fa52aa7a82f9226b3874a69816bda3af821f002 <ebdc569a07a3e8dbe66b4184922ad6f88ac0b96f
- Affected versionversion=4fa52aa7a82f9226b3874a69816bda3af821f002 <f1ac7789406e2ca9ac51c41ad2daa597f47bdd4d
- Affected versionversion=4fa52aa7a82f9226b3874a69816bda3af821f002 <f75617cc8df4155374132f0b500b0b3ebb967458
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo