Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-27398: Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout

Noroxi assessment

Priority: Monitor (action score 31/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.82% (FIRST EPSS); higher than 57.7% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 012363cb1bec5f33a7b94629ab2c1086f30280f2, 1b33d55fb7355e27f8c82cd4ecd560f162469249, 3212afd00e3cda790fd0583cb3eaef8f9575a014.

Low priority for now. Upgrade to Linux Linux 012363cb1bec5f33a7b94629ab2c1086f30280f2, 1b33d55fb7355e27f8c82cd4ecd560f162469249, 3212afd00e3cda790fd0583cb3eaef8f9575a014 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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] <TASK> [ 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] </TASK> [ 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---

HighCVSS 7.8 · v3.1—Proof of concept Fix available
Published
May 14, 2024
Updated
Aug 5, 2026
EPSS
0.8% · 57th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
8.0
0.2 point gap

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-27398

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
fedoraprojectfedora
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • fedoraproject fedora39
  • fedoraproject fedora40
  • linux linux kernel4.19.207 and later · before 4.19.314
  • linux linux kernel5.4.148 and later · before 5.4.276
  • linux linux kernel5.10.67 and later · before 5.10.217
  • linux linux kernel5.13.19 and later · before 5.14
  • linux linux kernel4.14.263 and later · before 4.15
  • linux linux kernel5.16 and later · before 6.1.91
  • linux linux kernel6.2 and later · before 6.6.31
  • linux linux kernel6.7 and later · before 6.8.10
  • linux linux kernel5.14.6 and later · before 5.15.159
  • linux linux kernel6.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • fea63ccd928c01573306983346588b26cffb5572, ec1f74319bb35c1c90c25014ec0f6ea6c3ca2134, b657bba82ff6a007d84fd076bd73b11131726a2b, 5.15affected
    • 48669c81a65628ef234cbdd91b9395952c7c27fe and later · before 1b33d55fb7355e27f8c82cd4ecd560f162469249affected · git
    • 37d7ae2b0578f2373674a755402ee722e96edc08 and later · before 3212afd00e3cda790fd0583cb3eaef8f9575a014affected · git
    • a1073aad497d0d071a71f61b721966a176d50c08 and later · before 33a6e92161a78c1073d90e27abe28d746feb0a53affected · git
    • ba316be1b6a00db7126ed9a39f9bee434a508043 and later · before 6a18eeb1b3bbc67c20d9609c31dca6a69b4bcde5affected · git
    • ba316be1b6a00db7126ed9a39f9bee434a508043 and later · before bfab2c1f7940a232cd519e82fff137e308abfd93affected · git
    • ba316be1b6a00db7126ed9a39f9bee434a508043 and later · before 012363cb1bec5f33a7b94629ab2c1086f30280f2affected · git
    • ba316be1b6a00db7126ed9a39f9bee434a508043 and later · before 50c2037fc28df870ef29d9728c770c8955d32178affected · git
    • ba316be1b6a00db7126ed9a39f9bee434a508043 and later · before 483bc08181827fc475643272ffb69c533007e546affected · git
    • 4.19.207 and later · before 4.19.314affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:10linux-5.10before 5.10.218-1~deb10u15.10.218-1~deb10u1
Debian:11linuxbefore 5.10.218-15.10.218-1
Debian:12linuxbefore 6.1.94-16.1.94-1
Debian:13linuxbefore 6.8.11-16.8.11-1
Red Hat:rhel_e4s:9.4::appstreambpftool-debuginfobefore 0:7.3.0-427.136.1.el9_40:7.3.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-64k-debug-develbefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-64k-debuginfobefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-64k-develbefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-debug-debuginfobefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-debug-develbefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-debuginfobefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-develbefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-devel-matchedbefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-docbefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4
Red Hat:rhel_e4s:9.4::appstreamkernel-rt-debuginfobefore 0:5.14.0-427.136.1.el9_40:5.14.0-427.136.1.el9_4

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-27393May 14, 2024 · xen-netfront: Add missing skb_mark_for_recycle
    30Monitor
  • ← EarlierCVE-2024-27394May 14, 2024 · tcp: Fix Use-After-Free in tcp_ao_connect_init
    31Monitor
  • Later →CVE-2024-27399May 14, 2024 · Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux012363cb1bec5f33a7b94629ab2c1086f30280f2Vendor (CNA)
Linux Linux1b33d55fb7355e27f8c82cd4ecd560f162469249Vendor (CNA)
Linux Linux3212afd00e3cda790fd0583cb3eaef8f9575a014Vendor (CNA)
Linux Linux33a6e92161a78c1073d90e27abe28d746feb0a53Vendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.19.314Vendor (CNA)
Linux Linux483bc08181827fc475643272ffb69c533007e546Vendor (CNA)
Linux Linux5.10.217Vendor (CNA)
Linux Linux5.14Vendor (CNA)
Linux Linux5.15Vendor (CNA)
Linux Linux5.4.276Vendor (CNA)
Linux Linux50c2037fc28df870ef29d9728c770c8955d32178Vendor (CNA)
Linux Linux6a18eeb1b3bbc67c20d9609c31dca6a69b4bcde5Vendor (CNA)
Linux Linuxbfab2c1f7940a232cd519e82fff137e308abfd93Vendor (CNA)
debian:linux6.1.94-1 · Debian:12Package registry (OSV)
debian:linux-5.105.10.218-1~deb10u1 · Debian:10Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstreamPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP2_Update_4411-150200.2.1 · SUSE:Linux Enterprise Live Patching 15 SP2Package registry (OSV)
suse:kernel-livepatch-SLE15-SP2_Update_466-150200.5.6.1 · SUSE:Linux Enterprise Live Patching 15 SP2Package registry (OSV)

+10

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:62025-03-08

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+298 d
  3. TodayNov 10, 2026+910 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (15 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records