Security readout for executives and security teams
Plain-English summary
This is a Linux kernel availability issue in AMD GPU compute handling. In SR-IOV setups, a failed reset can leave scheduling state stopped, and a later reset can panic the kernel. Business impact is service interruption, not data theft or privilege escalation based on the supplied sources.
Executive priority
Treat as a targeted availability risk. Patch during normal kernel maintenance unless exposed systems are business-critical GPU or virtualization hosts, where scheduling should be accelerated to reduce outage risk.
Technical view
The flaw is in drm/amd/amdkfd reset handling. After an SR-IOV ASIC reset fails, stop_cpsch may already have run and start_cpsch is not called because resume does not occur. A subsequent reset can repeat uninitialization and trigger a kernel panic. CVSS is 6.5: local, low-privilege, high availability impact.
Likely exposure
Exposure appears limited to Linux systems using AMD amdkfd GPU functionality in SR-IOV configurations on affected kernel builds. Cloud, VDI, GPU compute, or virtualized accelerator hosts are more plausible targets than standard desktops without this driver path.
Exploitation context
The bundle does not show CISA KEV listing or cited active exploitation. The CVSS vector requires local access with low privileges and no user interaction. Practical abuse would likely be denial of service against systems where an attacker can trigger the vulnerable reset path.
Researcher notes
Evidence is concise and patch-centered. The root condition is repeated reset handling after a failed SR-IOV ASIC reset. Sources support kernel panic availability impact, but do not provide public exploit details, broad exploitability evidence, or non-patch workarounds.
Mitigation direction
- Update affected Linux kernels to vendor releases containing the referenced stable fixes.
- Prioritize GPU virtualization, compute, and SR-IOV hosts using AMD amdkfd.
- Check Linux distribution advisories for exact package versions and backports.
- If patching is delayed, ask the vendor for supported temporary controls.
- Do not rely on generic hardening as a complete fix for this kernel panic.
Validation and detection
- Inventory Linux hosts with AMD GPU, amdkfd, and SR-IOV usage.
- Compare running kernel packages against distribution fixed versions or referenced stable commits.
- Review kernel logs for AMD KFD reset failures and panic events.
- Confirm patched hosts no longer run an affected kernel build.
- Document any unpatched GPU virtualization hosts as availability risk exceptions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-47551 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H24CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/74aafe99efb68f15e50be9f7032c2168512f98a8CVE reference, Linux
- https://git.kernel.org/stable/c/06c6f8f86ec243b89e52f0c3dc7062bcb9de74dfCVE reference, Linux
- https://git.kernel.org/stable/c/2cf49e00d40d5132e3d067b5aa6d84791929ab15CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.