Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2021-47369: s390/qeth: fix NULL deref in qeth_clear_working_pool_list()

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 248f064af222a1f97ee02c84a98013dfbccad386, 5.8, 5.9.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 248f064af222a1f97ee02c84a98013dfbccad386, 5.8, 5.9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 <hca@linux.ibm.com>

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-47369

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.7.16 and later · before 5.8
  • linux linux kernel5.8.2 and later · before 5.10.70
  • linux linux kernel5.11 and later · before 5.14.9
  • linux linux kernel5.15

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • b2400fe7e1011c5f3dc2268e8382082465b1c8a2, 22697ca855c06a4a1264d5651542b7d98870a8c4, 5.9affected
    • eff73e16ee116f6eafa2be48fab42659a27cb453 and later · before db94f89e1dadf693c15c2d60de0c34777cea5779affected · git
    • eff73e16ee116f6eafa2be48fab42659a27cb453 and later · before 9b00fb12cdc9d8d1c3ffe82a78e74738127803fcaffected · git
    • eff73e16ee116f6eafa2be48fab42659a27cb453 and later · before 248f064af222a1f97ee02c84a98013dfbccad386affected · git
    • 5.7.16 and later · before 5.8affected · semver
    • 5.8.2 and later · before 5.9affected · semver
    • before 5.9not affected · semver
    • 5.10.70 and later · up to and including 5.10.*not affected · semver
    • 5.14.9 and later · up to and including 5.14.*not affected · semver
    • 5.15 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.14.9-15.14.9-1
openSUSE:Leap 15.5dtb-aarch64before 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-64kbbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-azurebefore 5.14.21-150500.33.57.15.14.21-150500.33.57.1
openSUSE:Leap 15.5kernel-debugbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-defaultbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-default-basebefore 5.14.21-150500.55.68.1.150500.6.31.15.14.21-150500.55.68.1.150500.6.31.1
openSUSE:Leap 15.5kernel-docsbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-kvmsmallbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-obs-buildbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-obs-qabefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-rtbefore 5.14.21-150500.13.58.15.14.21-150500.13.58.1
openSUSE:Leap 15.5kernel-rt_debugbefore 5.14.21-150500.13.58.15.14.21-150500.13.58.1
openSUSE:Leap 15.5kernel-sourcebefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-source-azurebefore 5.14.21-150500.33.57.15.14.21-150500.33.57.1
openSUSE:Leap 15.5kernel-source-rtbefore 5.14.21-150500.13.58.15.14.21-150500.13.58.1
openSUSE:Leap 15.5kernel-symsbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap 15.5kernel-syms-azurebefore 5.14.21-150500.33.57.15.14.21-150500.33.57.1
openSUSE:Leap 15.5kernel-syms-rtbefore 5.14.21-150500.13.58.15.14.21-150500.13.58.1
openSUSE:Leap 15.5kernel-zfcpdumpbefore 5.14.21-150500.55.68.15.14.21-150500.55.68.1
openSUSE:Leap Micro 5.3kernel-defaultbefore 5.14.21-150400.24.122.25.14.21-150400.24.122.2
openSUSE:Leap Micro 5.3kernel-default-basebefore 5.14.21-150400.24.122.2.150400.24.58.25.14.21-150400.24.122.2.150400.24.58.2
openSUSE:Leap Micro 5.3kernel-rtbefore 5.14.21-150400.15.82.15.14.21-150400.15.82.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-64kbbefore 5.14.21-150400.24.122.25.14.21-150400.24.122.2

+27

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2021-47367May 21, 2024 · virtio-net: fix pages leaking when building skb in big mode
    22Monitor
  • ← EarlierCVE-2021-47368May 21, 2024 · enetc: Fix illegal access when reading affinity_hint
    28Monitor
  • Later →CVE-2021-47370May 21, 2024 · mptcp: ensure tx skbs always have the MPTCP ext
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux248f064af222a1f97ee02c84a98013dfbccad386Vendor (CNA)
Linux Linux5.8Vendor (CNA)
Linux Linux5.9Vendor (CNA)
Linux Linux9b00fb12cdc9d8d1c3ffe82a78e74738127803fcVendor (CNA)
Linux Linuxdb94f89e1dadf693c15c2d60de0c34777cea5779Vendor (CNA)
debian:linux5.14.9-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch645.14.21-150500.55.68.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-64kb5.14.21-150500.55.68.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-azure5.14.21-150500.33.57.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-debug5.14.21-150500.55.68.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-default5.14.21-150400.24.122.2 · openSUSE:Leap Micro 5.3Package registry (OSV)
opensuse:kernel-default-base5.14.21-150400.24.122.2.150400.24.58.2 · openSUSE:Leap Micro 5.3Package registry (OSV)
opensuse:kernel-rt5.14.21-150500.13.58.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-rt_debug5.14.21-150500.13.58.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-source-azure5.14.21-150500.33.57.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-source-rt5.14.21-150500.13.58.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-syms-azure5.14.21-150500.33.57.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-syms-rt5.14.21-150500.13.58.1 · openSUSE:Leap 15.5Package registry (OSV)
suse:kernel-64kb5.14.21-150400.24.122.2 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-azure5.14.21-150500.33.57.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5Package registry (OSV)
suse:kernel-default5.14.21-150400.24.122.2 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-default-base5.14.21-150400.24.122.2.150400.24.58.2 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-livepatch-SLE15-SP4_Update_271-150400.9.3.2 · SUSE:Linux Enterprise Live Patching 15 SP4Package registry (OSV)
suse:kernel-livepatch-SLE15-SP5-RT_Update_161-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5Package registry (OSV)
suse:kernel-rt5.14.21-150500.13.58.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-rt_debug5.14.21-150500.13.58.1 · SUSE:Real Time Module 15 SP5Package registry (OSV)
suse:kernel-source-azure5.14.21-150500.33.57.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5Package registry (OSV)
suse:kernel-source-rt5.14.21-150500.13.58.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-syms-azure5.14.21-150500.33.57.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5Package registry (OSV)
suse:kernel-syms-rt5.14.21-150500.13.58.1 · SUSE:Real Time Module 15 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records