CVE-2024-46746

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-09-18. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

HID: amd_sfh: free driver_data after destroying hid device

HID driver callbacks aren't called anymore once hid_destroy_device() has been called. Hence, hid driver_data should be freed only after the hid_destroy_device() function returned as driver_data is used in several callbacks.

I observed a crash with kernel 6.10.0 on my T14s Gen 3, after enabling KASAN to debug memory allocation, I got this output:

[ 13.050438] ================================================================== [ 13.054060] BUG: KASAN: slab-use-after-free in amd_sfh_get_report+0x3ec/0x530 [amd_sfh] [ 13.054809] psmouse serio1: trackpoint: Synaptics TrackPoint firmware: 0x02, buttons: 3/3 [ 13.056432] Read of size 8 at addr ffff88813152f408 by task (udev-worker)/479

[ 13.060970] CPU: 5 PID: 479 Comm: (udev-worker) Not tainted 6.10.0-arch1-2 #1 893bb55d7f0073f25c46adbb49eb3785fefd74b0 [ 13.063978] Hardware name: LENOVO 21CQCTO1WW/21CQCTO1WW, BIOS R22ET70W (1.40 ) 03/21/2024 [ 13.067860] Call Trace: [ 13.069383] input: TPPS/2 Synaptics TrackPoint as /devices/platform/i8042/serio1/input/input8 [ 13.071486] [ 13.071492] dump_stack_lvl+0x5d/0x80 [ 13.074870] snd_hda_intel 0000:33:00.6: enabling device (0000 -> 0002) [ 13.078296] ? amd_sfh_get_report+0x3ec/0x530 [amd_sfh 05f43221435b5205f734cd9da29399130f398a38] [ 13.082199] print_report+0x174/0x505 [ 13.085776] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 13.089367] ? srso_alias_return_thunk+0x5/0xfbef5 [ 13.093255] ? amd_sfh_get_report+0x3ec/0x530 [amd_sfh 05f43221435b5205f734cd9da29399130f398a38] [ 13.097464] kasan_report+0xc8/0x150 [ 13.101461] ? amd_sfh_get_report+0x3ec/0x530 [amd_sfh 05f43221435b5205f734cd9da29399130f398a38] [ 13.105802] amd_sfh_get_report+0x3ec/0x530 [amd_sfh 05f43221435b5205f734cd9da29399130f398a38] [ 13.110303] amdtp_hid_request+0xb8/0x110 [amd_sfh 05f43221435b5205f734cd9da29399130f398a38] [ 13.114879] ? srso_alias_return_thunk+0x5/0xfbef5 [ 13.119450] sensor_hub_get_feature+0x1d3/0x540 [hid_sensor_hub 3f13be3016ff415bea03008d45d99da837ee3082] [ 13.124097] hid_sensor_parse_common_attributes+0x4d0/0xad0 [hid_sensor_iio_common c3a5cbe93969c28b122609768bbe23efe52eb8f5] [ 13.127404] ? srso_alias_return_thunk+0x5/0xfbef5 [ 13.131925] ? __pfx_hid_sensor_parse_common_attributes+0x10/0x10 [hid_sensor_iio_common c3a5cbe93969c28b122609768bbe23efe52eb8f5] [ 13.136455] ? _raw_spin_lock_irqsave+0x96/0xf0 [ 13.140197] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 13.143602] ? devm_iio_device_alloc+0x34/0x50 [industrialio 3d261d5e5765625d2b052be40e526d62b1d2123b] [ 13.147234] ? srso_alias_return_thunk+0x5/0xfbef5 [ 13.150446] ? __devm_add_action+0x167/0x1d0 [ 13.155061] hid_gyro_3d_probe+0x120/0x7f0 [hid_sensor_gyro_3d 63da36a143b775846ab2dbb86c343b401b5e3172] [ 13.158581] ? srso_alias_return_thunk+0x5/0xfbef5 [ 13.161814] platform_probe+0xa2/0x150 [ 13.165029] really_probe+0x1e3/0x8a0 [ 13.168243] __driver_probe_device+0x18c/0x370 [ 13.171500] driver_probe_device+0x4a/0x120 [ 13.175000] __driver_attach+0x190/0x4a0 [ 13.178521] ? __pfx___driver_attach+0x10/0x10 [ 13.181771] bus_for_each_dev+0x106/0x180 [ 13.185033] ? __pfx__raw_spin_lock+0x10/0x10 [ 13.188229] ? __pfx_bus_for_each_dev+0x10/0x10 [ 13.191446] ? srso_alias_return_thunk+0x5/0xfbef5 [ 13.194382] bus_add_driver+0x29e/0x4d0 [ 13.197328] driver_register+0x1a5/0x360 [ 13.200283] ? __pfx_hid_gyro_3d_platform_driver_init+0x10/0x10 [hid_sensor_gyro_3d 63da36a143b775846ab2dbb86c343b401b5e3172] [ 13.203362] do_one_initcall+0xa7/0x380 [ 13.206432] ? __pfx_do_one_initcall+0x10/0x10 [ 13.210175] ? srso_alias_return_thunk+0x5/0xfbef5 [ 13.213211] ? kasan_unpoison+0x44/0x70 [ 13.216688] do_init_module+0x238/0x750 [ 13.2196 ---truncated---

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

September 18, 2024

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Aug 4, 2026
Patch available.
generic Patch Available

[SECURITY] [DLA 4008-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
generic

HID: amd_sfh: free driver_data after destroying hid device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/adb3e3c1ddb5a23b8b7122ef1913f528d728937c
generic

HID: amd_sfh: free driver_data after destroying hid device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/97155021ae17b86985121b33cf8098bcde00d497
generic

HID: amd_sfh: free driver_data after destroying hid device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86b4f5cf91ca03c08e3822ac89476a677a780bcc
generic

HID: amd_sfh: free driver_data after destroying hid device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/775125c7fe38533aaa4b20769f5b5e62cc1170a0
generic

HID: amd_sfh: free driver_data after destroying hid device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/60dc4ee0428d70bcbb41436b6729d29f1cbdfb89

Vendor Advisories for CVE-2024-46746(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1075.73) @ jammy2026-05-21ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1072.72) @ jammy2026-05-21ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1019.21~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1067.67) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04 (6.8.0-50.51) @ noble2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1038.42) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble2026-05-21ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-50.51~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1078.87~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-tools-azure (6.8.0-1020.23) @ noble2026-05-21ubuntu
linuxKernel @ 5.15.167—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u16.1.119-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (29 versions)6.1.112-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.10.11-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.10.11-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 144 total refreshes for this CVE.

  1. 2026-08-15 01:28 UTCEPSS rescore
  2. 2026-08-13 21:59 UTCEPSS rescore
  3. 2026-08-12 13:49 UTCEPSS rescore
  4. 2026-08-11 13:40 UTCEPSS rescore
  5. 2026-08-10 23:58 UTCEPSS rescore
  6. 2026-08-09 13:45 UTCEPSS rescore
  7. 2026-08-08 16:35 UTCEPSS rescore
  8. 2026-08-07 16:25 UTCEPSS rescore
  9. 2026-08-06 13:45 UTCEPSS rescore
  10. 2026-08-05 19:16 UTCEPSS rescore
  11. 2026-08-05 12:00 UTCEG score recompute
  12. 2026-08-05 12:00 UTCVendor advisory
  13. 2026-08-05 12:00 UTCGHSA enrichment
  14. 2026-08-04 15:08 UTCEPSS rescore
  15. 2026-08-04 11:48 UTCEG score recompute
  16. 2026-08-04 11:48 UTCVendor advisory
  17. 2026-08-04 11:48 UTCGHSA enrichment
  18. 2026-08-04 10:36 UTCEPSS rescore
  19. 2026-08-03 10:34 UTCEPSS rescore
  20. 2026-08-02 02:25 UTCEPSS rescore
  21. 2026-08-01 04:14 UTCEPSS rescore
  22. 2026-07-30 16:26 UTCEPSS rescore
  23. 2026-07-30 01:29 UTCEPSS rescore
  24. 2026-07-28 15:34 UTCEPSS rescore
  25. 2026-07-28 10:24 UTCOSV refresh
Show 75 more
  1. 2026-07-27 14:11 UTCEPSS rescore
  2. 2026-07-26 14:53 UTCEPSS rescore
  3. 2026-07-26 14:53 UTCEPSS rescore
  4. 2026-07-25 14:16 UTCEPSS rescore
  5. 2026-07-24 14:16 UTCEPSS rescore
  6. 2026-07-23 14:17 UTCEPSS rescore
  7. 2026-07-23 02:41 UTCEG score recompute
  8. 2026-07-22 14:07 UTCEPSS rescore
  9. 2026-07-21 15:23 UTCEPSS rescore
  10. 2026-07-21 15:23 UTCEPSS rescore
  11. 2026-07-20 17:06 UTCEPSS rescore
  12. 2026-07-19 14:30 UTCEPSS rescore
  13. 2026-07-19 14:30 UTCEPSS rescore
  14. 2026-07-19 02:28 UTCEPSS rescore
  15. 2026-07-19 02:28 UTCEPSS rescore
  16. 2026-07-18 10:03 UTCEPSS rescore
  17. 2026-07-18 10:03 UTCEPSS rescore
  18. 2026-07-16 17:02 UTCEPSS rescore
  19. 2026-07-15 16:56 UTCEPSS rescore
  20. 2026-07-15 16:56 UTCEPSS rescore
  21. 2026-07-15 01:59 UTCEPSS rescore
  22. 2026-07-15 01:59 UTCEPSS rescore
  23. 2026-07-13 22:29 UTCEPSS rescore
  24. 2026-07-13 06:12 UTCEPSS rescore
  25. 2026-07-12 05:45 UTCEPSS rescore
  26. 2026-07-12 05:45 UTCEPSS rescore
  27. 2026-07-11 08:26 UTCEPSS rescore
  28. 2026-07-11 02:11 UTCOSV refresh
  29. 2026-07-09 19:09 UTCEPSS rescore
  30. 2026-07-09 19:09 UTCEPSS rescore
  31. 2026-07-08 15:14 UTCEPSS rescore
  32. 2026-07-07 13:45 UTCEPSS rescore
  33. 2026-07-06 16:26 UTCEPSS rescore
  34. 2026-07-06 02:22 UTCEPSS rescore
  35. 2026-07-06 02:22 UTCEPSS rescore
  36. 2026-07-01 15:05 UTCEPSS rescore
  37. 2026-06-30 23:21 UTCEPSS rescore
  38. 2026-06-30 23:21 UTCEPSS rescore
  39. 2026-06-29 14:05 UTCEPSS rescore
  40. 2026-06-28 14:07 UTCEPSS rescore
  41. 2026-06-28 14:06 UTCEPSS rescore
  42. 2026-06-28 04:55 UTCEPSS rescore
  43. 2026-06-28 04:55 UTCEPSS rescore
  44. 2026-06-27 03:07 UTCEPSS rescore
  45. 2026-06-27 03:07 UTCEPSS rescore
  46. 2026-06-25 13:49 UTCEPSS rescore
  47. 2026-06-24 14:04 UTCEPSS rescore
  48. 2026-06-24 14:04 UTCEPSS rescore
  49. 2026-06-23 21:32 UTCEPSS rescore
  50. 2026-06-23 21:32 UTCEPSS rescore
  51. 2026-06-22 14:25 UTCEPSS rescore
  52. 2026-06-22 14:25 UTCEPSS rescore
  53. 2026-06-22 09:32 UTCOSV refresh
  54. 2026-06-21 14:55 UTCEPSS rescore
  55. 2026-06-21 01:58 UTCEPSS rescore
  56. 2026-06-21 01:58 UTCEPSS rescore
  57. 2026-06-19 19:25 UTCEPSS rescore
  58. 2026-06-19 19:25 UTCEPSS rescore
  59. 2026-06-18 17:52 UTCEPSS rescore
  60. 2026-06-18 17:52 UTCEPSS rescore
  61. 2026-06-16 17:52 UTCEPSS rescore
  62. 2026-06-16 17:52 UTCEPSS rescore
  63. 2026-06-15 17:47 UTCEPSS rescore
  64. 2026-06-14 23:17 UTCEPSS rescore
  65. 2026-06-13 22:59 UTCEPSS rescore
  66. 2026-06-13 22:59 UTCEPSS rescore
  67. 2026-06-13 22:59 UTCEPSS rescore
  68. 2026-06-12 23:11 UTCEPSS rescore
  69. 2026-06-12 23:11 UTCEPSS rescore
  70. 2026-06-11 13:59 UTCEPSS rescore
  71. 2026-06-10 22:18 UTCEPSS rescore
  72. 2026-06-10 13:21 UTCEPSS rescore
  73. 2026-06-08 14:16 UTCEPSS rescore
  74. 2026-06-08 14:16 UTCEPSS rescore
  75. 2026-06-07 15:24 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-46746?
CVE-2024-46746 is a high vulnerability published on September 18, 2024. In the Linux kernel, the following vulnerability has been resolved: HID: amdsfh: free driverdata after destroying hid device HID driver callbacks aren't called anymore once hiddestroydevice() has been called. Hence, hid driver_data should be freed only after the hiddestroydevice() function returned…
When was CVE-2024-46746 disclosed?
CVE-2024-46746 was first published in the National Vulnerability Database on September 18, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-46746 actively exploited?
CVE-2024-46746 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.7% of all scored CVEs.
What is the CVSS score of CVE-2024-46746?
CVE-2024-46746 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-46746?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-46746, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-46746

Explore →

Is Your Infrastructure Affected by CVE-2024-46746?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs