CVE-2024-58013

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 2025-02-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-2025-5200 (ENISA EUVD) · GHSA-qg99-hc5r-rhvg (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.2%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: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync

This fixes the following crash:

================================================================== BUG: KASAN: slab-use-after-free in mgmt_remove_adv_monitor_sync+0x3a/0xd0 net/bluetooth/mgmt.c:5543 Read of size 8 at addr ffff88814128f898 by task kworker/u9:4/5961

CPU: 1 UID: 0 PID: 5961 Comm: kworker/u9:4 Not tainted 6.12.0-syzkaller-10684-gf1cd565ce577 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: hci0 hci_cmd_sync_work Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x169/0x550 mm/kasan/report.c:489 kasan_report+0x143/0x180 mm/kasan/report.c:602 mgmt_remove_adv_monitor_sync+0x3a/0xd0 net/bluetooth/mgmt.c:5543 hci_cmd_sync_work+0x22b/0x400 net/bluetooth/hci_sync.c:332 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

Allocated by task 16026: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0x98/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __kmalloc_cache_noprof+0x243/0x390 mm/slub.c:4314 kmalloc_noprof include/linux/slab.h:901 [inline] kzalloc_noprof include/linux/slab.h:1037 [inline] mgmt_pending_new+0x65/0x250 net/bluetooth/mgmt_util.c:269 mgmt_pending_add+0x36/0x120 net/bluetooth/mgmt_util.c:296 remove_adv_monitor+0x102/0x1b0 net/bluetooth/mgmt.c:5568 hci_mgmt_cmd+0xc47/0x11d0 net/bluetooth/hci_sock.c:1712 hci_sock_sendmsg+0x7b8/0x11c0 net/bluetooth/hci_sock.c:1832 sock_sendmsg_nosec net/socket.c:711 [inline] __sock_sendmsg+0x221/0x270 net/socket.c:726 sock_write_iter+0x2d7/0x3f0 net/socket.c:1147 new_sync_write fs/read_write.c:586 [inline] vfs_write+0xaeb/0xd30 fs/read_write.c:679 ksys_write+0x18f/0x2b0 fs/read_write.c:731 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 16022: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:582 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2338 [inline] slab_free mm/slub.c:4598 [inline] kfree+0x196/0x420 mm/slub.c:4746 mgmt_pending_foreach+0xd1/0x130 net/bluetooth/mgmt_util.c:259 __mgmt_power_off+0x183/0x430 net/bluetooth/mgmt.c:9550 hci_dev_close_sync+0x6c4/0x11c0 net/bluetooth/hci_sync.c:5208 hci_dev_do_close net/bluetooth/hci_core.c:483 [inline] hci_dev_close+0x112/0x210 net/bluetooth/hci_core.c:508 sock_do_ioctl+0x158/0x460 net/socket.c:1209 sock_ioctl+0x626/0x8e0 net/socket.c:1328 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:906 [inline] __se_sys_ioctl+0xf5/0x170 fs/ioctl.c:892 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f

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.2% × 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.2%
EPSS %ILE
15th
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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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

February 27, 2025

Last Modified

October 15, 2026

Advisory Details (5)

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

Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26fbd3494a7dd26269cb0817c289267dbcfdec06
Web page

Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ebbcb9bc794e5be647ee28fdf14eb1ae0659405
Web page

Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/75e65b983c5e2ee51962bfada98a79d805f28827

Patch Availability(14)

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 rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.128-1~deb11u1 (6 versions)
  • every version up to 6.1.129-1~deb11u1: fixed in 6.1.129-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (35 versions)
  • every version up to 6.1.129-1: fixed in 6.1.129-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.15-1: fixed in 6.12.15-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.15-1: fixed in 6.12.15-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(12)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2024-58013?
CVE-2024-58013 is a high-severity vulnerability; its CVE record was published on February 27, 2025. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync This fixes the following crash: ================================================================== BUG: KASAN: slab-use-after-free in…
When was the CVE record for CVE-2024-58013 published?
The CVE record for CVE-2024-58013 was published on February 27, 2025. 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-58013 actively exploited?
CVE-2024-58013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-58013?
CVE-2024-58013 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-58013?
A fix for CVE-2024-58013 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-58013 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-58013

Explore →

Is Your Infrastructure Affected by CVE-2024-58013?

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