CVE-2024-56653

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-53301 (ENISA EUVD) · GHSA-jgxj-ff5p-q3r5 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

Bluetooth: btmtk: avoid UAF in btmtk_process_coredump

hci_devcd_append may lead to the release of the skb, so it cannot be accessed once it is called.

================================================================== BUG: KASAN: slab-use-after-free in btmtk_process_coredump+0x2a7/0x2d0 [btmtk] Read of size 4 at addr ffff888033cfabb0 by task kworker/0:3/82

CPU: 0 PID: 82 Comm: kworker/0:3 Tainted: G U 6.6.40-lockdep-03464-g1d8b4eb3060e #1 b0b3c1cc0c842735643fb411799d97921d1f688c Hardware name: Google Yaviks_Ufs/Yaviks_Ufs, BIOS Google_Yaviks_Ufs.15217.552.0 05/07/2024 Workqueue: events btusb_rx_work [btusb] Call Trace: dump_stack_lvl+0xfd/0x150 print_report+0x131/0x780 kasan_report+0x177/0x1c0 btmtk_process_coredump+0x2a7/0x2d0 [btmtk 03edd567dd71a65958807c95a65db31d433e1d01] btusb_recv_acl_mtk+0x11c/0x1a0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] btusb_rx_work+0x9e/0xe0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30

Allocated by task 82: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 __kasan_slab_alloc+0x4e/0x60 kmem_cache_alloc+0x19f/0x360 skb_clone+0x132/0xf70 btusb_recv_acl_mtk+0x104/0x1a0 [btusb] btusb_rx_work+0x9e/0xe0 [btusb] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30

Freed by task 1733: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 kasan_save_free_info+0x28/0xb0 ____kasan_slab_free+0xfd/0x170 kmem_cache_free+0x183/0x3f0 hci_devcd_rx+0x91a/0x2060 [bluetooth] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30

The buggy address belongs to the object at ffff888033cfab40 which belongs to the cache skbuff_head_cache of size 232 The buggy address is located 112 bytes inside of freed 232-byte region [ffff888033cfab40, ffff888033cfac28)

The buggy address belongs to the physical page: page:00000000a174ba93 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x33cfa head:00000000a174ba93 order:1 entire_mapcount:0 nr_pages_mapped:0 pincount:0 anon flags: 0x4000000000000840(slab|head|zone=1) page_type: 0xffffffff() raw: 4000000000000840 ffff888100848a00 0000000000000000 0000000000000001 raw: 0000000000000000 0000000080190019 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff888033cfaa80: fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc ffff888033cfab00: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb >ffff888033cfab80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888033cfac00: fb fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc ffff888033cfac80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================

Check if we need to call hci_devcd_complete before calling hci_devcd_append. That requires that we check data->cd_info.cnt >= MTK_COREDUMP_NUM instead of data->cd_info.cnt > MTK_COREDUMP_NUM, as we increment data->cd_info.cnt only once the call to hci_devcd_append succeeds.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 27, 2024

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
Patch available.
Web page

Bluetooth: btmtk: avoid UAF in btmtk_process_coredump - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ecdcaea0e4057171ea4c3783e1cc1c900ad99125
Web page

Bluetooth: btmtk: avoid UAF in btmtk_process_coredump - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d20ff1d3cb40479789368f502eedb0a00e4161fc
Web page

Bluetooth: btmtk: avoid UAF in btmtk_process_coredump - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b548f5e9456c568155499d9ebac675c0d7a296e8

Vendor Advisories for CVE-2024-56653(2)

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

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-21.21) @ oracular2026-10-27ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1011.12) @ oracular2026-10-27ubuntu
ubuntulinux-tools-lowlatency-hwe-24.04-edge (6.11.0-1011.12~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1017.17) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi (6.11.0-1010.10) @ oracular2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-59.61~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-27ubuntu
ubuntuoracle (5.4.0-1121) @ focal2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1021.22) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1028.33~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1028.33) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1016.17) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-27ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 6.6.67 (fixes >=6.6.0)—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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.6-1: fixed in 6.12.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.6-1: fixed in 6.12.6-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(13)

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 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 217 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 122 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-10-27 19:52 UTCEG score recompute
  7. 2026-10-27 19:52 UTCVendor advisory
  8. 2026-10-27 19:52 UTCGHSA enrichmentGHSA-jgxj-ff5p-q3r5 · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-25 16:55 UTCEG score recompute
  12. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-19 15:21 UTCEG score recompute
  20. 2026-10-19 15:21 UTCVendor advisory
  21. 2026-10-19 15:21 UTCGHSA enrichmentGHSA-jgxj-ff5p-q3r5 · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-10-18 05:58 UTCEG score recompute
  24. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
Show 70 more
  1. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-10-12 17:37 UTCEG score recompute
  5. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-10-11 21:03 UTCEG score recompute
  7. 2026-10-11 15:54 UTCEG score recompute
  8. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-10-02 16:25 UTCEG score recompute
  18. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-09-27 04:15 UTCOSV refresh
  23. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  26. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  27. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  28. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  29. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  30. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  31. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  32. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  33. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  34. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  35. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  36. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  37. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  39. 2026-09-07 13:18 UTCOSV refresh
  40. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  41. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  42. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  43. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  44. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  45. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  46. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  47. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  48. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  49. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  50. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  51. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  52. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  53. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  54. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  55. 2026-08-20 22:31 UTCOSV refresh
  56. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  57. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  58. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  59. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  60. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  61. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  62. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  63. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  64. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  65. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  66. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  67. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  68. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  69. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  70. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-56653?
CVE-2024-56653 is a high-severity vulnerability; its CVE record was published on December 27, 2024. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtk: avoid UAF in btmtk_process_coredump hci_devcd_append may lead to the release of the skb, so it cannot be accessed once it is called. ================================================================== BUG: KASAN:…
When was the CVE record for CVE-2024-56653 published?
The CVE record for CVE-2024-56653 was published on December 27, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-56653 actively exploited?
CVE-2024-56653 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56653?
CVE-2024-56653 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-56653?
A fix for CVE-2024-56653 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-56653 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-56653?

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

Book a Demo →Browse All CVEs