Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the AMD Sensor Fusion Hub HID driver. Affected systems can fail to free small request objects after sensor processing. The provided sources do not show remote attack, code execution, data theft, or active exploitation.
Executive priority
Treat as a routine kernel maintenance item unless affected AMD sensor-enabled endpoints are widely deployed or showing memory pressure. No source indicates emergency exploitation, but kernel fixes should not be deferred indefinitely.
Technical view
Kmemleak found an unreferenced allocation in the amd_sfh driver path involving amd_sfh_get_report and amdtp_hid_request during HID sensor handling. The resolved bug frees a request_list entry after the processed entry is removed from that list.
Likely exposure
Exposure appears limited to Linux systems using the amd_sfh HID sensor driver. The source lists Linux 5.11, 5.12.10, and 5.13 version data, but distro backports and exact package status must be verified locally.
Exploitation context
CISA KEV status is false in the bundle, and no cited source reports active exploitation. The evidence describes a memory leak found by kernel leak detection, not an exploit chain.
Researcher notes
The public record is sparse: no CVSS, CWE, exploitability assessment, or distro-specific matrix is included. Analysis should focus on kernel provenance, driver reachability, and whether downstream kernels backported the stable commits.
Mitigation direction
- Check vendor or distribution kernel advisories for CVE-2021-47133 status.
- Update to a kernel containing the referenced stable fixes.
- Prioritize AMD client systems using HID sensor features.
- Use normal change control and reboot planning for kernel updates.
Validation and detection
- Inventory Linux hosts and identify kernel versions in the listed affected range.
- Check whether the amd_sfh driver is present or loaded.
- Confirm distribution packages include the upstream stable fix commits.
- Monitor for kernel memory pressure on affected endpoints until patched.
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.
CVE-2021-47133 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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
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/29beadea66a226d744d5ffdcde6b984623053d24CVE reference, Linux
- https://git.kernel.org/stable/c/5ad755fd2b326aa2bc8910b0eb351ee6aece21b1CVE 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.