CVE-2021-47369

s390/qeth: fix NULL deref in qeth_clear_working_pool_list()

MEDIUM
5.5
CVSS Score
Published: May 21, 2024 at 03:03 PM UTC
Updated: June 17, 2026 at 04:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: s390/qeth: fix NULL deref in qeth_clear_working_pool_list() When qeth_set_online() calls qeth_clear_working_pool_list() to roll back after an error exit from qeth_hardsetup_card(), we are at risk of accessing card->qdio.in_q before it was allocated by qeth_alloc_qdio_queues() via qeth_mpc_initialize(). qeth_clear_working_pool_list() then dereferences NULL, and by writing to queue->bufs[i].pool_entry scribbles all over the CPU's lowcore. Resulting in a crash when those lowcore areas are used next (eg. on the next machine-check interrupt). Such a scenario would typically happen when the device is first set online and its queues aren't allocated yet. An early IO error or certain misconfigs (eg. mismatched transport mode, bad portno) then cause us to error out from qeth_hardsetup_card() with card->qdio.in_q still being NULL. Fix it by checking the pointer for NULL before accessing it. Note that we also have (rare) paths inside qeth_mpc_initialize() where a configuration change can cause us to free the existing queues, expecting that subsequent code will allocate them again. If we then error out before that re-allocation happens, the same bug occurs. Root-caused-by: Heiko Carstens <[email protected]>

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.7.16v ≥ 5.8.25.11 ≤ v < 5.14.95.7.16 ≤ v < 5.85.8.2 ≤ v < 5.10.705.8.2 ≤ v < 5.95.9 ≤ v < 5.10.705.9 ≤ v < 5.14.95.9 ≤ v < 5.1522697ca855c06a4a1264d5651542b7d98870a8c45.15 rc15.15 rc25.7.165.8.2b2400fe7e1011c5f3dc2268e8382082465b1c8a2eff73e16ee11eff73e16ee116f6eafa2be48fab42659a27cb453
Vendor states this is fixed in 248f064af222 (fixed)
Vendor states this is fixed in 248f064af222a1f97ee02c84a98013dfbccad386 (fixed)
Vendor states this is fixed in 9b00fb12cdc9 (fixed)
Vendor states this is fixed in 9b00fb12cdc9d8d1c3ffe82a78e74738127803fc (fixed)
Vendor states this is fixed in db94f89e1dad (fixed)
Vendor states this is fixed in db94f89e1dadf693c15c2d60de0c34777cea5779 (fixed)
Vendor states this is fixed in 5.10.70 (unaffected)
Vendor states this is fixed in 5.14.9 (unaffected)
Vendor states this is fixed in 5.15 (unaffected)
Affected range stops below 5.8, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.9 (unaffected)

References (3)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/248f064af222a1f97ee02c84a98013dfbccad386
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9b00fb12cdc9d8d1c3ffe82a78e74738127803fc
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/db94f89e1dadf693c15c2d60de0c34777cea5779

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card