CVE-2022-48636
s390/dasd: fix Oops in dasd_alias_get_start_dev due to missing pavgroup
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: s390/dasd: fix Oops in dasd_alias_get_start_dev due to missing pavgroup Fix Oops in dasd_alias_get_start_dev() function caused by the pavgroup pointer being NULL. The pavgroup pointer is checked on the entrance of the function but without the lcu->lock being held. Therefore there is a race window between dasd_alias_get_start_dev() and _lcu_update() which sets pavgroup to NULL with the lcu->lock held. Fix by checking the pavgroup pointer with lcu->lock held.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.25
References 8
git.kernel.org
- stable/c/d86b4267834e6d4af62e3073e48166e349ab1b70
- stable/c/49f401a98b318761ca2e15d4c7869a20043fbed4
- stable/c/aaba5ff2742043705bc4c02fd0b2b246e2e16da1
- stable/c/2e473351400e3dd66f0b71eddcef82ee45a584c1
- stable/c/f5fcc9d6d71d9ff7fdbdd4b89074e6e24fffc20b
- stable/c/d3a67c21b18f33c79382084af556557c442f12a6
- stable/c/650a2e79d176db753654d3dde88e53a2033036ac
- stable/c/db7ba07108a48c0f95b74fabbfd5d63e924f992d