Review reviewHigh

CVE-2022-48636

Linux Linux, linux kernel

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.

CVSS
7.8
EPSS
0.24%
14.5% percentile
CISA KEV
Not listed
Published
2024.04.28
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.24%
Technical severityCVSS 7.8

Vulnerability overview

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.

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 8e09f21574ea3028d5629e5de759e0b196c690c5 < d86b4267834e6d4af62e3073e48166e349ab1b70, >= 8e09f21574ea3028d5629e5de759e0b196c690c5 < 49f401a98b318761ca2e15d4c7869a20043fbed4, >= 8e09f21574ea3028d5629e5de759e0b196c690c5 < aaba5ff2742043705bc4c02fd0b2b246e2e16da1, >= 8e09f21574ea3028d5629e5de759e0b196c690c5 < 2e473351400e3dd66f0b71eddcef82ee45a584c1, >= 8e09f21574ea3028d5629e5de759e0b196c690c5 < f5fcc9d6d71d9ff7fdbdd4b89074e6e24fffc20b, >= 8e09f21574ea3028d5629e5de759e0b196c690c5 < d3a67c21b18f33c79382084af556557c442f12a6, >= 8e09f21574ea3028d5629e5de759e0b196c690c5 < 650a2e79d176db753654d3dde88e53a2033036ac, >= 8e09f21574ea3028d5629e5de759e0b196c690c5 < db7ba07108a48c0f95b74fabbfd5d63e924f992d, >= 2.6.25, >= 2.6.25 < 4.9.330, >= 4.10 < 4.14.295, >= 4.15 < 4.19.260, >= 4.20 < 5.4.215, >= 5.5 < 5.10.146, >= 5.11 < 5.15.71, >= 5.16 < 5.19.12, 6.0
Fixed versions
4.9.330, 4.14.295, 4.19.260, 5.4.215, 5.10.146, 5.15.71, 5.19.12

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-476
CVE-2022-48636 — Linux Linux, linux kernel | SECUFOCUS NOW