CVE-2024-27398

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-05-14. 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 weekElevated

Also known asEUVD-2024-24602 (ENISA EUVD) · GHSA-45cm-4v3w-5jpw (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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

Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout

When the sco connection is established and then, the sco socket is releasing, timeout_work will be scheduled to judge whether the sco disconnection is timeout. The sock will be deallocated later, but it is dereferenced again in sco_sock_timeout. As a result, the use-after-free bugs will happen. The root cause is shown below:

Cleanup Thread | Worker Thread sco_sock_release | sco_sock_close | __sco_sock_close | sco_sock_set_timer | schedule_delayed_work | sco_sock_kill | (wait a time) sock_put(sk) //FREE | sco_sock_timeout | sock_hold(sk) //USE

The KASAN report triggered by POC is shown below:

[ 95.890016] ================================================================== [ 95.890496] BUG: KASAN: slab-use-after-free in sco_sock_timeout+0x5e/0x1c0 [ 95.890755] Write of size 4 at addr ffff88800c388080 by task kworker/0:0/7 ... [ 95.890755] Workqueue: events sco_sock_timeout [ 95.890755] Call Trace: [ 95.890755] [ 95.890755] dump_stack_lvl+0x45/0x110 [ 95.890755] print_address_description+0x78/0x390 [ 95.890755] print_report+0x11b/0x250 [ 95.890755] ? __virt_addr_valid+0xbe/0xf0 [ 95.890755] ? sco_sock_timeout+0x5e/0x1c0 [ 95.890755] kasan_report+0x139/0x170 [ 95.890755] ? update_load_avg+0xe5/0x9f0 [ 95.890755] ? sco_sock_timeout+0x5e/0x1c0 [ 95.890755] kasan_check_range+0x2c3/0x2e0 [ 95.890755] sco_sock_timeout+0x5e/0x1c0 [ 95.890755] process_one_work+0x561/0xc50 [ 95.890755] worker_thread+0xab2/0x13c0 [ 95.890755] ? pr_cont_work+0x490/0x490 [ 95.890755] kthread+0x279/0x300 [ 95.890755] ? pr_cont_work+0x490/0x490 [ 95.890755] ? kthread_blkcg+0xa0/0xa0 [ 95.890755] ret_from_fork+0x34/0x60 [ 95.890755] ? kthread_blkcg+0xa0/0xa0 [ 95.890755] ret_from_fork_asm+0x11/0x20 [ 95.890755] [ 95.890755] [ 95.890755] Allocated by task 506: [ 95.890755] kasan_save_track+0x3f/0x70 [ 95.890755] __kasan_kmalloc+0x86/0x90 [ 95.890755] __kmalloc+0x17f/0x360 [ 95.890755] sk_prot_alloc+0xe1/0x1a0 [ 95.890755] sk_alloc+0x31/0x4e0 [ 95.890755] bt_sock_alloc+0x2b/0x2a0 [ 95.890755] sco_sock_create+0xad/0x320 [ 95.890755] bt_sock_create+0x145/0x320 [ 95.890755] __sock_create+0x2e1/0x650 [ 95.890755] __sys_socket+0xd0/0x280 [ 95.890755] __x64_sys_socket+0x75/0x80 [ 95.890755] do_syscall_64+0xc4/0x1b0 [ 95.890755] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 95.890755] [ 95.890755] Freed by task 506: [ 95.890755] kasan_save_track+0x3f/0x70 [ 95.890755] kasan_save_free_info+0x40/0x50 [ 95.890755] poison_slab_object+0x118/0x180 [ 95.890755] __kasan_slab_free+0x12/0x30 [ 95.890755] kfree+0xb2/0x240 [ 95.890755] __sk_destruct+0x317/0x410 [ 95.890755] sco_sock_release+0x232/0x280 [ 95.890755] sock_close+0xb2/0x210 [ 95.890755] __fput+0x37f/0x770 [ 95.890755] task_work_run+0x1ae/0x210 [ 95.890755] get_signal+0xe17/0xf70 [ 95.890755] arch_do_signal_or_restart+0x3f/0x520 [ 95.890755] syscall_exit_to_user_mode+0x55/0x120 [ 95.890755] do_syscall_64+0xd1/0x1b0 [ 95.890755] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 95.890755] [ 95.890755] The buggy address belongs to the object at ffff88800c388000 [ 95.890755] which belongs to the cache kmalloc-1k of size 1024 [ 95.890755] The buggy address is located 128 bytes inside of [ 95.890755] freed 1024-byte region [ffff88800c388000, ffff88800c388400) [ 95.890755] [ 95.890755] The buggy address belongs to the physical page: [ 95.890755] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff88800c38a800 pfn:0xc388 [ 95.890755] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [ 95.890755] ano ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
51
EG Risk 51/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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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.8%
EPSS %ILE
57th
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.8% 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 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

May 14, 2024

Last Modified

August 5, 2026

Advisory Details (10)

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

oss-security - Re: Linux: Race can lead to UAF in net/bluetooth/sco.c: sco_sock_connect()

http://www.openwall.com/lists/oss-security/2024/11/30/1
Web page

oss-security - Linux: Race can lead to UAF in net/bluetooth/sco.c: sco_sock_connect()

http://www.openwall.com/lists/oss-security/2024/11/29/1
Web page

Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a18eeb1b3bbc67c20d9609c31dca6a69b4bcde5
Web page

Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50c2037fc28df870ef29d9728c770c8955d32178
Web page

Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/483bc08181827fc475643272ffb69c533007e546
Web page

Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33a6e92161a78c1073d90e27abe28d746feb0a53
Web page

Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3212afd00e3cda790fd0583cb3eaef8f9575a014
Web page

Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b33d55fb7355e27f8c82cd4ecd560f162469249
Web page

Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/012363cb1bec5f33a7b94629ab2c1086f30280f2

Vendor Advisories for CVE-2024-27398(2)

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

Patch Availability(25)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1135.129) @ focal2026-10-28ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1135.142~18.04.1) @ bionic2026-10-28ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.128~20.04.1) @ focal2026-10-28ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1114.126~18.04.1) @ bionic2026-10-28ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-10-28ubuntu
ubuntuoracle (5.15.0-1055) @ jammy2026-10-28ubuntu
ubuntulinux-tools-azure (6.8.0-1012.14) @ noble2026-10-28ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1065.71~20.04.1) @ focal2026-10-28ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1129.138~18.04.1) @ bionic2026-10-28ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1065.61) @ jammy2026-10-28ubuntu
ubuntulinux-tools-bluefield (5.4.0.1090.86) @ focal2026-10-28ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-10-28ubuntu
ubuntuoracle (4.15.0-1129) @ bionic2026-10-28ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1010.10) @ noble2026-10-28ubuntu
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-10-28ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1049 (5.4.0-1049.53) @ focal2026-10-28ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-10-28ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.229.241~16.04.1) @ xenial2026-10-28ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1060.58) @ jammy2026-10-28ubuntu
ubuntulinux-tools-azure (4.15.0-1181.196~14.04.1) @ trusty2026-10-28ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.118) @ jammy2026-10-28ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1070.68) @ jammy2026-10-28ubuntu
redhatkernel-0:5.14.0-427.136.1.el9_42026-07-08redhat
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 4.19.314 (fixes >=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

(6 across 5 ecosystems)
Debian:10(2)
PackageVulnerable rangeFix by version rangeDependents
linux4.19.118-1 ... 4.19.98-1~bpo9+1 (46 versions)
  • every version up to 4.19.316-1: fixed in 4.19.316-1
—
linux-5.105.10.136-1~deb10u1 ... 5.10.216-1~deb10u1 (14 versions)
  • every version up to 5.10.218-1~deb10u1: fixed in 5.10.218-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (40 versions)
  • every version up to 5.10.218-1: fixed in 5.10.218-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.94-1~bpo11+1 (23 versions)
  • every version up to 6.1.94-1: fixed in 6.1.94-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.11-1: fixed in 6.8.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.11-1: fixed in 6.8.11-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(22)

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 / 42× 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 94 of 230 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 136 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCsecunnix/CVE-2024-27398
    Published Mar 8, 2025

    CVE-2024-27398 POC

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-27398?
CVE-2024-27398 is a high-severity vulnerability; its CVE record was published on May 14, 2024. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout When the sco connection is established and then, the sco socket is releasing, timeout_work will be scheduled to judge whether the sco disconnection is timeout. The sock…
When was the CVE record for CVE-2024-27398 published?
The CVE record for CVE-2024-27398 was published on May 14, 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-27398 actively exploited?
CVE-2024-27398 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-27398?
CVE-2024-27398 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-27398?
A fix for CVE-2024-27398 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-27398 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-27398

Explore →

Is Your Infrastructure Affected by CVE-2024-27398?

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

Book a Demo →Browse All CVEs