Kernel crash via unlocked pavgroup race
Published Apr 28, 2024 · Updated Aug 5, 2026
NULL pointer dereference in the Linux kernel s390 DASD driver allows local users to crash the kernel through a device-update race. dasd_alias_get_start_dev() checks pavgroup without holding lcu->lock, allowing _lcu_update() to clear the pointer before it is dereferenced. Reaching the flaw requires local low-privileged access and use of the affected s390 DASD alias path; the bounded consequence is a kernel Oops and service interruption.
Summary
What happened
NULL pointer dereference in the Linux kernel s390 DASD driver allows local users to crash the kernel through a device-update race. dasd_alias_get_start_dev() checks pavgroup without holding lcu->lock, allowing _lcu_update() to clear the pointer before it is dereferenced. Reaching the flaw requires local low-privileged access and use of the affected s390 DASD alias path; the bounded consequence is a kernel Oops and service interruption.
The record
- CVE
- CVE-2022-48636
- Published
- Apr 28, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 28, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=2.6.25
- Affected versionversion=8e09f21574ea3028d5629e5de759e0b196c690c5 <2e473351400e3dd66f0b71eddcef82ee45a584c1
- Affected versionversion=8e09f21574ea3028d5629e5de759e0b196c690c5 <49f401a98b318761ca2e15d4c7869a20043fbed4
- Affected versionversion=8e09f21574ea3028d5629e5de759e0b196c690c5 <650a2e79d176db753654d3dde88e53a2033036ac
- Affected versionversion=8e09f21574ea3028d5629e5de759e0b196c690c5 <aaba5ff2742043705bc4c02fd0b2b246e2e16da1
- Affected versionversion=8e09f21574ea3028d5629e5de759e0b196c690c5 <d3a67c21b18f33c79382084af556557c442f12a6
- Affected versionversion=8e09f21574ea3028d5629e5de759e0b196c690c5 <d86b4267834e6d4af62e3073e48166e349ab1b70
- Affected versionversion=8e09f21574ea3028d5629e5de759e0b196c690c5 <db7ba07108a48c0f95b74fabbfd5d63e924f992d
- Affected versionversion=8e09f21574ea3028d5629e5de759e0b196c690c5 <f5fcc9d6d71d9ff7fdbdd4b89074e6e24fffc20b
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