CVE-2021-47551: drm/amd/amdkfd: Fix kernel panic when reset failed and been triggered again
Noroxi assessment
Priority: Monitor (action score 31/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.28% (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 06c6f8f86ec243b89e52f0c3dc7062bcb9de74df, 2cf49e00d40d5132e3d067b5aa6d84791929ab15, 74aafe99efb68f15e50be9f7032c2168512f98a8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 06c6f8f86ec243b89e52f0c3dc7062bcb9de74df, 2cf49e00d40d5132e3d067b5aa6d84791929ab15, 74aafe99efb68f15e50be9f7032c2168512f98a8 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/amd/amdkfd: Fix kernel panic when reset failed and been triggered again In SRIOV configuration, the reset may failed to bring asic back to normal but stop cpsch already been called, the start_cpsch will not be called since there is no resume in this case. When reset been triggered again, driver should avoid to do uninitialization again.
- Published
- May 24, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 21th percentile
- CWE
- CWE-770
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 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
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
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.
Is your version affected? Check itNoroxi 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 helpAffected 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 |
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.5affected
- 2c99a547bcf9bb8532abd2953479949018449f93 and later · before 74aafe99efb68f15e50be9f7032c2168512f98a8affected · git
- 2c99a547bcf9bb8532abd2953479949018449f93 and later · before 06c6f8f86ec243b89e52f0c3dc7062bcb9de74dfaffected · git
- 2c99a547bcf9bb8532abd2953479949018449f93 and later · before 2cf49e00d40d5132e3d067b5aa6d84791929ab15affected · git
- before 5.5not affected · semver
- 5.10.84 and later · up to and including 5.10.*not affected · semver
- 5.15.7 and later · up to and including 5.15.*not affected · semver
- 5.16 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.10.84
- linux linux kernel5.11 and later · before 5.15.7
- linux linux kernel5.16
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.15.15-1 | 5.15.15-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47549May 24, 2024 · sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl31Monitor
- ← EarlierCVE-2021-47550May 24, 2024 · drm/amd/amdgpu: fix potential memleak22Monitor
- Later →CVE-2021-47552May 24, 2024 · blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and disk_release()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 | 06c6f8f86ec243b89e52f0c3dc7062bcb9de74df | Vendor (CNA) |
| Linux Linux | 2cf49e00d40d5132e3d067b5aa6d84791929ab15 | Vendor (CNA) |
| Linux Linux | 74aafe99efb68f15e50be9f7032c2168512f98a8 | Vendor (CNA) |
| debian:linux | 5.15.15-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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2021-4713760 days apartnet: lantiq: fix memory corruption in RX ring39Monitor
- CVE-2024-359694 days apartipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr35Monitor
- CVE-2024-3402731 days apartf2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock31Monitor
- CVE-2021-4713070 days apartnvmet: fix freeing unallocated p2pmem30Monitor
- CVE-2024-2689437 days apartACPI: processor_idle: Fix memory leak in acpi_processor_power_exit()24Monitor
- CVE-2023-5252983 days apartHID: sony: Fix a potential memory leak in sony_probe()24Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0551 · May 27, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.