Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw can cause the AMD Sensor Fusion Hub driver to use memory after it has been freed. The supplied evidence documents a kernel crash. Exploitation requires local, low-privilege access, and affected systems could potentially lose confidentiality, integrity, or availability, supporting the 7.8 high-severity rating.
Executive priority
Treat this as a high-priority endpoint patching issue, especially on shared Linux workstations or systems allowing untrusted local access. It is not presented as remotely exploitable or actively exploited. Use normal expedited kernel maintenance, focusing first on confirmed amd_sfh exposure rather than assuming every Linux host is vulnerable.
Technical view
The amd_sfh HID teardown path freed driver_data before hid_destroy_device() completed. HID callbacks could still access that data, producing a slab use-after-free in amd_sfh_get_report. The correction reverses the cleanup order so driver_data is freed after the HID device is destroyed. A crash was observed on kernel 6.10.0 with KASAN enabled.
Likely exposure
Exposure is limited to Linux systems using the affected amd_sfh driver, typically compatible AMD Sensor Fusion Hub hardware. The bundle identifies affected kernel lines beginning with 5.11 and lists stable correction points including 5.15.167, 6.1.110, 6.6.51, and 6.10.10. Distribution backports may alter exact exposure.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. The supplied sources demonstrate a crash and use-after-free but provide no exploit demonstration. This CVE is not listed as KEV in the bundle, and there is no supplied evidence of active exploitation.
Researcher notes
The evidence supports a callback-lifetime error during HID device destruction. The observable failure is a slab use-after-free read in amd_sfh_get_report during sensor probing. Stable commits are supplied for multiple kernel branches. The bundle does not establish reliable privilege escalation, code execution, or exploitation in the wild; those outcomes should not be asserted without additional evidence.
Mitigation direction
- Upgrade to a vendor-supported kernel containing the applicable stable fix or distribution backport.
- Prioritize endpoints that load amd_sfh and permit access by untrusted local users.
- Consult distribution advisories to confirm the corrected package version for each deployed kernel branch.
- If immediate updating is impossible, seek vendor guidance on safely disabling unused affected hardware support.
Validation and detection
- Inventory running kernel versions and identify systems loading or using the amd_sfh module.
- Compare installed kernel packages against vendor advisories and the referenced stable correction commits.
- Reboot after updating and confirm the corrected kernel is running.
- Review kernel logs for amd_sfh crashes, KASAN findings, or related use-after-free reports.
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-2024-46746 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
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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/86b4f5cf91ca03c08e3822ac89476a677a780bccCVE reference, Linux
- https://git.kernel.org/stable/c/775125c7fe38533aaa4b20769f5b5e62cc1170a0CVE reference, Linux
- https://git.kernel.org/stable/c/60dc4ee0428d70bcbb41436b6729d29f1cbdfb89CVE reference, Linux
- https://git.kernel.org/stable/c/adb3e3c1ddb5a23b8b7122ef1913f528d728937cCVE reference, Linux
- https://git.kernel.org/stable/c/97155021ae17b86985121b33cf8098bcde00d497CVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlCVE reference, CVE
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.