Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-53237: Bluetooth: fix use-after-free in device_for_each_child()

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.31% (FIRST EPSS).
  • 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 0f67ca2a80acf8b207240405b7f72d660665d3df, 27aabf27fd014ae037cc179c61b0bee7cff55b3d, 4.20; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.

Low priority for now. Upgrade to Linux Linux 0f67ca2a80acf8b207240405b7f72d660665d3df, 27aabf27fd014ae037cc179c61b0bee7cff55b3d, 4.20; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 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 in device_for_each_child() Syzbot has reported the following KASAN splat: BUG: KASAN: slab-use-after-free in device_for_each_child+0x18f/0x1a0 Read of size 8 at addr ffff88801f605308 by task kbnepd bnep0/4980 CPU: 0 UID: 0 PID: 4980 Comm: kbnepd bnep0 Not tainted 6.12.0-rc4-00161-gae90f6a6170d #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x100/0x190 ? device_for_each_child+0x18f/0x1a0 print_report+0x13a/0x4cb ? __virt_addr_valid+0x5e/0x590 ? __phys_addr+0xc6/0x150 ? device_for_each_child+0x18f/0x1a0 kasan_report+0xda/0x110 ? device_for_each_child+0x18f/0x1a0 ? __pfx_dev_memalloc_noio+0x10/0x10 device_for_each_child+0x18f/0x1a0 ? __pfx_device_for_each_child+0x10/0x10 pm_runtime_set_memalloc_noio+0xf2/0x180 netdev_unregister_kobject+0x1ed/0x270 unregister_netdevice_many_notify+0x123c/0x1d80 ? __mutex_trylock_common+0xde/0x250 ? __pfx_unregister_netdevice_many_notify+0x10/0x10 ? trace_contention_end+0xe6/0x140 ? __mutex_lock+0x4e7/0x8f0 ? __pfx_lock_acquire.part.0+0x10/0x10 ? rcu_is_watching+0x12/0xc0 ? unregister_netdev+0x12/0x30 unregister_netdevice_queue+0x30d/0x3f0 ? __pfx_unregister_netdevice_queue+0x10/0x10 ? __pfx_down_write+0x10/0x10 unregister_netdev+0x1c/0x30 bnep_session+0x1fb3/0x2ab0 ? __pfx_bnep_session+0x10/0x10 ? __pfx_lock_release+0x10/0x10 ? __pfx_woken_wake_function+0x10/0x10 ? __kthread_parkme+0x132/0x200 ? __pfx_bnep_session+0x10/0x10 ? kthread+0x13a/0x370 ? __pfx_bnep_session+0x10/0x10 kthread+0x2b7/0x370 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x48/0x80 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 4974: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 __kmalloc_noprof+0x1d1/0x440 hci_alloc_dev_priv+0x1d/0x2820 __vhci_create_device+0xef/0x7d0 vhci_write+0x2c7/0x480 vfs_write+0x6a0/0xfc0 ksys_write+0x12f/0x260 do_syscall_64+0xc7/0x250 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 4979: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x4f/0x70 kfree+0x141/0x490 hci_release_dev+0x4d9/0x600 bt_host_release+0x6a/0xb0 device_release+0xa4/0x240 kobject_put+0x1ec/0x5a0 put_device+0x1f/0x30 vhci_release+0x81/0xf0 __fput+0x3f6/0xb30 task_work_run+0x151/0x250 do_exit+0xa79/0x2c30 do_group_exit+0xd5/0x2a0 get_signal+0x1fcd/0x2210 arch_do_signal_or_restart+0x93/0x780 syscall_exit_to_user_mode+0x140/0x290 do_syscall_64+0xd4/0x250 entry_SYSCALL_64_after_hwframe+0x77/0x7f In 'hci_conn_del_sysfs()', 'device_unregister()' may be called when an underlying (kobject) reference counter is greater than 1. This means that reparenting (happened when the device is actually freed) is delayed and, during that delay, parent controller device (hciX) may be deleted. Since the latter may create a dangling pointer to freed parent, avoid that scenario by reparenting to NULL explicitly.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Dec 27, 2024
Updated
Aug 5, 2026
EPSS
0.3% · 24th 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.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
8.8
1.0 point gap

CVSS:3.1/AV:A/AC:L/PR:N/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
  • No public exploit code on record
  • A fix has been released

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

Follow CVE-2024-53237

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

Affected versions

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

  • linux linux kernel4.19.300 and later · before 4.20
  • linux linux kernel5.4.262 and later · before 5.5
  • linux linux kernel5.10.202 and later · before 5.10.231
  • linux linux kernel5.15.140 and later · before 5.15.174
  • linux linux kernel6.1.64 and later · before 6.1.120
  • linux linux kernel6.5.13 and later · before 6.6
  • linux linux kernel6.6.3 and later · before 6.6.64
  • linux linux kernel6.7 and later · before 6.11.11
  • linux linux kernel6.12 and later · before 6.12.2

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

    • 5c53afc766e07098429520b7677eaa164b593451, fc666d1b47518a18519241cae213de1babd4a4ba, 6.7affected
    • 3c4236f1b2a715e878a06599fa8b0cc21f165d28 and later · before 6894717a1ea363c5a27010ba604f957c309d282daffected · git
    • 53d61daf35b1bbf3ae06e852ee107aa2f05b3776 and later · before fb91ce37dc9a37ea23cf32b6d7b667004e93d4c5affected · git
    • ba7088769800d9892a7e4f35c3137a5b3e65410b and later · before a9584c897d1cba6265c78010bbb45ca5722c88bcaffected · git
    • 87624b1f9b781549e69f92db7ede012a21cec275 and later · before 0f67ca2a80acf8b207240405b7f72d660665d3dfaffected · git
    • 56a4fdde95ed98d864611155f6728983e199e198 and later · before de5a44f351ca7efd9add9851b218f5353e2224b7affected · git
    • a85fb91e3d728bdfc80833167e8162cce8bc7004 and later · before 91e2a2e4d1336333804cd31162984f01ad8cc70faffected · git
    • a85fb91e3d728bdfc80833167e8162cce8bc7004 and later · before 7b277bd569bb6a2777f0014f84b4344f444fd49daffected · git
    • a85fb91e3d728bdfc80833167e8162cce8bc7004 and later · before 27aabf27fd014ae037cc179c61b0bee7cff55b3daffected · git
    • 5.4.262 and later · before 5.4.297affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.123-16.1.123-1
Debian:13linuxbefore 6.12.3-16.12.3-1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_5before 8-150600.2.18-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_0before 14-150600.3.114-150600.3.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_5before 7-150600.2.17-150600.2.1
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0_Update_2before 4-1.14-1.1
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0_Update_3before 4-1.24-1.2
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0_Update_4before 3-1.23-1.2
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0-RT_Update_2before 4-1.14-1.1
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0-RT_Update_3before 4-1.24-1.2
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0-RT_Update_4before 2-1.12-1.1

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-53235Dec 27, 2024 · erofs: fix file-backed mounts over FUSE
    22Monitor
  • ← EarlierCVE-2024-53236Dec 27, 2024 · xsk: Free skb when TX metadata options are invalid
    22Monitor
  • Later →CVE-2024-53238Dec 27, 2024 · Bluetooth: btmtk: adjust the position to init iso data anchor
    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 Linux0f67ca2a80acf8b207240405b7f72d660665d3dfVendor (CNA)
Linux Linux27aabf27fd014ae037cc179c61b0bee7cff55b3dVendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux5.10.231Vendor (CNA)
Linux Linux5.15.174Vendor (CNA)
Linux Linux5.4.297Vendor (CNA)
Linux Linux6.1.120Vendor (CNA)
Linux Linux6.6Vendor (CNA)
Linux Linux6.6.64Vendor (CNA)
Linux Linux6894717a1ea363c5a27010ba604f957c309d282dVendor (CNA)
Linux Linux7b277bd569bb6a2777f0014f84b4344f444fd49dVendor (CNA)
Linux Linux91e2a2e4d1336333804cd31162984f01ad8cc70fVendor (CNA)
Linux Linuxa9584c897d1cba6265c78010bbb45ca5722c88bcVendor (CNA)
Linux Linuxde5a44f351ca7efd9add9851b218f5353e2224b7Vendor (CNA)
Linux Linuxfb91ce37dc9a37ea23cf32b6d7b667004e93d4c5Vendor (CNA)
azl3 kernel 6.6.57.1-7 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.64.2-1 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-2 on CBL Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-2 on CBL-Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.176.3-1 on CBL Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.123-1 · Debian:12Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0_Update_24-1.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0_Update_34-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0_Update_43-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_24-1.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_34-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_42-1.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_58-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_014-150600.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_57-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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 (9 more)

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

All records