CVE-2024-26890

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

Score 6.5 from GitHub Security Advisory published 2024-04-17. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-24152 (ENISA EUVD) · GHSA-9pfj-cx2g-pfp8 (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

Bluetooth: btrtl: fix out of bounds memory access

The problem is detected by KASAN. btrtl driver uses private hci data to store 'struct btrealtek_data'. If btrtl driver is used with btusb, then memory for private hci data is allocated in btusb. But no private data is allocated after hci_dev, when btrtl is used with hci_h5.

This commit adds memory allocation for hci_h5 case.

================================================================== BUG: KASAN: slab-out-of-bounds in btrtl_initialize+0x6cc/0x958 [btrtl] Write of size 8 at addr ffff00000f5a5748 by task kworker/u9:0/76

Hardware name: Pine64 PinePhone (1.2) (DT) Workqueue: hci0 hci_power_on [bluetooth] Call trace: dump_backtrace+0x9c/0x128 show_stack+0x20/0x38 dump_stack_lvl+0x48/0x60 print_report+0xf8/0x5d8 kasan_report+0x90/0xd0 __asan_store8+0x9c/0xc0 [btrtl] h5_btrtl_setup+0xd0/0x2f8 [hci_uart] h5_setup+0x50/0x80 [hci_uart] hci_uart_setup+0xd4/0x260 [hci_uart] hci_dev_open_sync+0x1cc/0xf68 [bluetooth] hci_dev_do_open+0x34/0x90 [bluetooth] hci_power_on+0xc4/0x3c8 [bluetooth] process_one_work+0x328/0x6f0 worker_thread+0x410/0x778 kthread+0x168/0x178 ret_from_fork+0x10/0x20

Allocated by task 53: kasan_save_stack+0x3c/0x68 kasan_save_track+0x20/0x40 kasan_save_alloc_info+0x68/0x78 __kasan_kmalloc+0xd4/0xd8 __kmalloc+0x1b4/0x3b0 hci_alloc_dev_priv+0x28/0xa58 [bluetooth] hci_uart_register_device+0x118/0x4f8 [hci_uart] h5_serdev_probe+0xf4/0x178 [hci_uart] serdev_drv_probe+0x54/0xa0 really_probe+0x254/0x588 __driver_probe_device+0xc4/0x210 driver_probe_device+0x64/0x160 __driver_attach_async_helper+0x88/0x158 async_run_entry_fn+0xd0/0x388 process_one_work+0x328/0x6f0 worker_thread+0x410/0x778 kthread+0x168/0x178 ret_from_fork+0x10/0x20

Last potentially related work creation: kasan_save_stack+0x3c/0x68 __kasan_record_aux_stack+0xb0/0x150 kasan_record_aux_stack_noalloc+0x14/0x20 __queue_work+0x33c/0x960 queue_work_on+0x98/0xc0 hci_recv_frame+0xc8/0x1e8 [bluetooth] h5_complete_rx_pkt+0x2c8/0x800 [hci_uart] h5_rx_payload+0x98/0xb8 [hci_uart] h5_recv+0x158/0x3d8 [hci_uart] hci_uart_receive_buf+0xa0/0xe8 [hci_uart] ttyport_receive_buf+0xac/0x178 flush_to_ldisc+0x130/0x2c8 process_one_work+0x328/0x6f0 worker_thread+0x410/0x778 kthread+0x168/0x178 ret_from_fork+0x10/0x20

Second to last potentially related work creation: kasan_save_stack+0x3c/0x68 __kasan_record_aux_stack+0xb0/0x150 kasan_record_aux_stack_noalloc+0x14/0x20 __queue_work+0x788/0x960 queue_work_on+0x98/0xc0 __hci_cmd_sync_sk+0x23c/0x7a0 [bluetooth] __hci_cmd_sync+0x24/0x38 [bluetooth] btrtl_initialize+0x760/0x958 [btrtl] h5_btrtl_setup+0xd0/0x2f8 [hci_uart] h5_setup+0x50/0x80 [hci_uart] hci_uart_setup+0xd4/0x260 [hci_uart] hci_dev_open_sync+0x1cc/0xf68 [bluetooth] hci_dev_do_open+0x34/0x90 [bluetooth] hci_power_on+0xc4/0x3c8 [bluetooth] process_one_work+0x328/0x6f0 worker_thread+0x410/0x778 kthread+0x168/0x178 ret_from_fork+0x10/0x20 ==================================================================

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.6%
EPSS %ILE
48th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

April 17, 2024

Last Modified

August 5, 2026

Advisory Details (4)

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

Bluetooth: btrtl: fix out of bounds memory access - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: btrtl: fix out of bounds memory access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0c657e641df1e77d6087688190f632cad9c0439b
Web page

Bluetooth: btrtl: fix out of bounds memory access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2f232bc389a4f5943c40733582f9edf77b89e499
Web page

Bluetooth: btrtl: fix out of bounds memory access - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2024-26890(1)

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

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-35.35) @ noble2026-10-24ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1006.6) @ noble2026-10-24ubuntu
ubuntulinux-tools-gcp (6.8.0-1008.9) @ noble2026-10-24ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1006.6+1) @ noble2026-10-24ubuntu
ubuntulinux-tools-oem-22.04d (6.5.0.1027.29) @ jammy2026-10-24ubuntu
ubuntulinux-tools-gcp (6.5.0.1024.26~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-starfive (6.5.0.1017.18~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04 (6.5.0.44.44~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-gke (6.8.0-1004.7) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.5.0.44.44) @ mantic2026-10-24ubuntu
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
linuxKernel @ 6.6.23 (fixes >=6.2.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.7.12-1: fixed in 6.7.12-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-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 / 39× 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 97 of 215 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 118 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-26890?
CVE-2024-26890 is a medium-severity vulnerability; its CVE record was published on April 17, 2024. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: fix out of bounds memory access The problem is detected by KASAN. btrtl driver uses private hci data to store 'struct btrealtek_data'. If btrtl driver is used with btusb, then memory for private hci data is…
When was the CVE record for CVE-2024-26890 published?
The CVE record for CVE-2024-26890 was published on April 17, 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-26890 actively exploited?
CVE-2024-26890 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26890?
CVE-2024-26890 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2024-26890?
A fix for CVE-2024-26890 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-26890 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-26890

Explore →

Is Your Infrastructure Affected by CVE-2024-26890?

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

Book a Demo →Browse All CVEs