CVE-2024-27398

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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, ghsa, nvd
Trending — 4 sources updated this weekElevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.8Exploit: Elevated riskExposed: 0

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.8(medium)
EG Risk
51(Track)
EG Risk 51/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
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

May 14, 2024

Last Modified

August 5, 2026

Advisory Details (10)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

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
generic🟡 PoC Available

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
generic

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
generic

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
generic

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
generic

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
generic

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
generic

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
generic

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
generic

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(24)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-427.136.1.el9_42026-07-08redhat
ubuntulinux-tools-oem-24.04a (6.8.0-1010.10) @ noble2026-05-24ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.192.212~18.04.1) @ bionic2026-05-24ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1070.68) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-05-24ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1065.71~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1129.122) @ focal2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-05-24ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1065.61) @ jammy2026-05-24ubuntu
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1135.129) @ focal2026-05-24ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1060.58) @ jammy2026-05-24ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1135.142~18.04.1) @ bionic2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.128~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-tools-bluefield (5.4.0.1090.86) @ focal2026-05-24ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1114.126~18.04.1) @ bionic2026-05-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.229.241~16.04.1) @ xenial2026-05-24ubuntu
ubuntuoracle (5.4.0-1121) @ focal2026-05-24ubuntu
ubuntulowlatency-4.4 (4.4.0-243) @ xenial2026-05-24ubuntu
ubuntulinux-tools-azure (4.15.0-1181.196~14.04.1) @ trusty2026-05-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.118) @ jammy2026-05-24ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 4.19.314—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.

Weakness Classification(1)

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

Additional Vendor Advisories

(21)

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 14× in last 7d / 49× 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 135 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

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

    CVE-2024-27398 POC

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-27398?
CVE-2024-27398 is a high vulnerability published on May 14, 2024. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use-after-free bugs caused by scosocktimeout 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 CVE-2024-27398 disclosed?
CVE-2024-27398 was first published in the National Vulnerability Database on May 14, 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-27398 actively exploited?
CVE-2024-27398 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.1% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-27398, 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs