NVD / CVE Program· CNA Linux

CVE-2021-47421: drm/amdgpu: handle the case of pci_channel_io_frozen only in amdgpu_pci_resume

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.20% (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 248b061689a40f4fed05252ee2c89f87cf26d7d8, 72e9a1bf9b722628c28092e0c2cd8717edd201dc, 785cc093b6b5a93cc350421a55f3f1eda6585156.
Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 248b061689a40f4fed05252ee2c89f87cf26d7d8, 72e9a1bf9b722628c28092e0c2cd8717edd201dc, 785cc093b6b5a93cc350421a55f3f1eda6585156 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: drm/amdgpu: handle the case of pci_channel_io_frozen only in amdgpu_pci_resume In current code, when a PCI error state pci_channel_io_normal is detectd, it will report PCI_ERS_RESULT_CAN_RECOVER status to PCI driver, and PCI driver will continue the execution of PCI resume callback report_resume by pci_walk_bridge, and the callback will go into amdgpu_pci_resume finally, where write lock is releasd unconditionally without acquiring such lock first. In this case, a deadlock will happen when other threads start to acquire the read lock. To fix this, add a member in amdgpu_device strucutre to cache pci_channel_state, and only continue the execution in amdgpu_pci_resume when it's pci_channel_io_frozen.

MediumCVSS 5.5 · v3.1—No exploit Fix available

Denial of service

Published: May 21, 2024
Updated: Aug 5, 2026
EPSS: 0.2% · 10th percentile
CWE: CWE-667

Report tools

JSON

Action score

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.

CNA vs NVD score

NVD: 5.5
CNA · Linux: 7.8; 2.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Running WordPress? Scan your site free with WP Lens

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.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_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.10 and later · before 5.10.241
linux linux kernel5.11 and later · before 5.14.12
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
- 5.10affected
- c9a6b82f45e261d247b980a7949aaa6a9bfffe01 and later · before 785cc093b6b5a93cc350421a55f3f1eda6585156affected · git
- c9a6b82f45e261d247b980a7949aaa6a9bfffe01 and later · before 72e9a1bf9b722628c28092e0c2cd8717edd201dcaffected · git
- c9a6b82f45e261d247b980a7949aaa6a9bfffe01 and later · before 248b061689a40f4fed05252ee2c89f87cf26d7d8affected · git
- before 5.10not affected · semver
- 5.10.241 and later · up to and including 5.10.*not affected · semver
- 5.14.12 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.

Ecosystem	Package	Affected range	Fix
Debian:11	linux	before 5.10.244-1	5.10.244-1
Debian:12	linux	before 5.14.12-1	5.14.12-1

Same product

linux: all records

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-47419May 21, 2024 · net/sched: sch_taprio: properly cancel timer from taprio_destroy()
22Monitor
← EarlierCVE-2021-47420May 21, 2024 · drm/amdkfd: fix a potential ttm->sg memory leak
22Monitor
Later →CVE-2021-47422May 21, 2024 · drm/nouveau/kms/nv50-: fix file release memory leak
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 / package	Fixed version	Source
Linux Linux	248b061689a40f4fed05252ee2c89f87cf26d7d8	Vendor (CNA)
Linux Linux	72e9a1bf9b722628c28092e0c2cd8717edd201dc	Vendor (CNA)
Linux Linux	785cc093b6b5a93cc350421a55f3f1eda6585156	Vendor (CNA)
debian:linux	5.14.12-1 · Debian:12	Package 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.

Credits

All researchers

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).