CVE-2024-46680

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-09-13. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

Bluetooth: btnxpuart: Fix random crash seen while removing driver

This fixes the random kernel crash seen while removing the driver, when running the load/unload test over multiple iterations.

1) modprobe btnxpuart 2) hciconfig hci0 reset 3) hciconfig (check hci0 interface up with valid BD address) 4) modprobe -r btnxpuart Repeat steps 1 to 4

The ps_wakeup() call in btnxpuart_close() schedules the psdata->work(), which gets scheduled after module is removed, causing a kernel crash.

This hidden issue got highlighted after enabling Power Save by default in 4183a7be7700 (Bluetooth: btnxpuart: Enable Power Save feature on startup)

The new ps_cleanup() deasserts UART break immediately while closing serdev device, cancels any scheduled ps_work and destroys the ps_lock mutex.

[ 85.884604] Unable to handle kernel paging request at virtual address ffffd4a61638f258 [ 85.884624] Mem abort info: [ 85.884625] ESR = 0x0000000086000007 [ 85.884628] EC = 0x21: IABT (current EL), IL = 32 bits [ 85.884633] SET = 0, FnV = 0 [ 85.884636] EA = 0, S1PTW = 0 [ 85.884638] FSC = 0x07: level 3 translation fault [ 85.884642] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000041dd0000 [ 85.884646] [ffffd4a61638f258] pgd=1000000095fff003, p4d=1000000095fff003, pud=100000004823d003, pmd=100000004823e003, pte=0000000000000000 [ 85.884662] Internal error: Oops: 0000000086000007 [#1] PREEMPT SMP [ 85.890932] Modules linked in: algif_hash algif_skcipher af_alg overlay fsl_jr_uio caam_jr caamkeyblob_desc caamhash_desc caamalg_desc crypto_engine authenc libdes crct10dif_ce polyval_ce polyval_generic snd_soc_imx_spdif snd_soc_imx_card snd_soc_ak5558 snd_soc_ak4458 caam secvio error snd_soc_fsl_spdif snd_soc_fsl_micfil snd_soc_fsl_sai snd_soc_fsl_utils gpio_ir_recv rc_core fuse [last unloaded: btnxpuart(O)] [ 85.927297] CPU: 1 PID: 67 Comm: kworker/1:3 Tainted: G O 6.1.36+g937b1be4345a #1 [ 85.936176] Hardware name: FSL i.MX8MM EVK board (DT) [ 85.936182] Workqueue: events 0xffffd4a61638f380 [ 85.936198] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 85.952817] pc : 0xffffd4a61638f258 [ 85.952823] lr : 0xffffd4a61638f258 [ 85.952827] sp : ffff8000084fbd70 [ 85.952829] x29: ffff8000084fbd70 x28: 0000000000000000 x27: 0000000000000000 [ 85.963112] x26: ffffd4a69133f000 x25: ffff4bf1c8540990 x24: ffff4bf215b87305 [ 85.963119] x23: ffff4bf215b87300 x22: ffff4bf1c85409d0 x21: ffff4bf1c8540970 [ 85.977382] x20: 0000000000000000 x19: ffff4bf1c8540880 x18: 0000000000000000 [ 85.977391] x17: 0000000000000000 x16: 0000000000000133 x15: 0000ffffe2217090 [ 85.977399] x14: 0000000000000001 x13: 0000000000000133 x12: 0000000000000139 [ 85.977407] x11: 0000000000000001 x10: 0000000000000a60 x9 : ffff8000084fbc50 [ 85.977417] x8 : ffff4bf215b7d000 x7 : ffff4bf215b83b40 x6 : 00000000000003e8 [ 85.977424] x5 : 00000000410fd030 x4 : 0000000000000000 x3 : 0000000000000000 [ 85.977432] x2 : 0000000000000000 x1 : ffff4bf1c4265880 x0 : 0000000000000000 [ 85.977443] Call trace: [ 85.977446] 0xffffd4a61638f258 [ 85.977451] 0xffffd4a61638f3e8 [ 85.977455] process_one_work+0x1d4/0x330 [ 85.977464] worker_thread+0x6c/0x430 [ 85.977471] kthread+0x108/0x10c [ 85.977476] ret_from_fork+0x10/0x20 [ 85.977488] Code: bad PC value [ 85.977491] ---[ end trace 0000000000000000 ]---

Preset since v6.9.11

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

September 13, 2024

Last Modified

August 5, 2026

Vendor Advisories for CVE-2024-46680(1)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04 (6.8.0-50.51) @ noble2026-05-23ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble2026-05-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1019.21.1) @ noble2026-05-23ubuntu
ubuntulinux-tools-azure (6.8.0-1020.23) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-50.51~22.04.1) @ jammy2026-05-23ubuntu
linuxKernel @ 6.6.49osv

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.10.9-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.10.9-1

Additional Vendor Advisories

(5)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2024-46680?
CVE-2024-46680 is a medium vulnerability published on September 13, 2024. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btnxpuart: Fix random crash seen while removing driver This fixes the random kernel crash seen while removing the driver, when running the load/unload test over multiple iterations. 1) modprobe btnxpuart 2) hciconfig…
When was CVE-2024-46680 disclosed?
CVE-2024-46680 was first published in the National Vulnerability Database on September 13, 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-46680 actively exploited?
CVE-2024-46680 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.9% of all scored CVEs.
What is the CVSS score of CVE-2024-46680?
CVE-2024-46680 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-46680?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-46680, 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-46680

Explore →

Is Your Infrastructure Affected by CVE-2024-46680?

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