Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26801: Bluetooth: Avoid potential use-after-free in hci_error_reset

Noroxi assessment

Priority: Monitor (action score 22/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.42% (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 2449007d3f73b2842c9734f45f0aadb522daf592, 2ab9a19d896f5a0dd386e1f001c5309bc35f433b, 45085686b9559bfbe3a4f41d3d695a520668f5e1.
  • Severity is disputed: the assigning authority (CNA) scores it 8.8, NVD 5.5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 2449007d3f73b2842c9734f45f0aadb522daf592, 2ab9a19d896f5a0dd386e1f001c5309bc35f433b, 45085686b9559bfbe3a4f41d3d695a520668f5e1 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: Avoid potential use-after-free in hci_error_reset While handling the HCI_EV_HARDWARE_ERROR event, if the underlying BT controller is not responding, the GPIO reset mechanism would free the hci_dev and lead to a use-after-free in hci_error_reset. Here's the call trace observed on a ChromeOS device with Intel AX201: queue_work_on+0x3e/0x6c __hci_cmd_sync_sk+0x2ee/0x4c0 [bluetooth <HASH:3b4a6>] ? init_wait_entry+0x31/0x31 __hci_cmd_sync+0x16/0x20 [bluetooth <HASH:3b4a 6>] hci_error_reset+0x4f/0xa4 [bluetooth <HASH:3b4a 6>] process_one_work+0x1d8/0x33f worker_thread+0x21b/0x373 kthread+0x13a/0x152 ? pr_cont_work+0x54/0x54 ? kthread_blkcg+0x31/0x31 ret_from_fork+0x1f/0x30 This patch holds the reference count on the hci_dev while processing a HCI_EV_HARDWARE_ERROR event to avoid potential crash.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 4, 2024
Updated
Aug 5, 2026
EPSS
0.4% · 37th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
8.8
3.3 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-26801

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.

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.0 and later · before 4.19.309
  • linux linux kernel4.20 and later · before 5.4.271
  • linux linux kernel5.5 and later · before 5.10.212
  • linux linux kernel5.11 and later · before 5.15.151
  • linux linux kernel5.16 and later · before 6.1.81
  • linux linux kernel6.2 and later · before 6.6.21
  • linux linux kernel6.7 and later · before 6.7.9
  • linux linux kernel6.8

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

    • 4.0affected
    • c7741d16a57cbf97eebe53f27e8216b1ff20e20c and later · before e0b278650f07acf2e0932149183458468a731c03affected · git
    • c7741d16a57cbf97eebe53f27e8216b1ff20e20c and later · before 98fb98fd37e42fd4ce13ff657ea64503e24b6090affected · git
    • c7741d16a57cbf97eebe53f27e8216b1ff20e20c and later · before 6dd0a9dfa99f8990a08eb8fdd8e79bee31c7d8e2affected · git
    • c7741d16a57cbf97eebe53f27e8216b1ff20e20c and later · before da4569d450b193e39e87119fd316c0291b585d14affected · git
    • c7741d16a57cbf97eebe53f27e8216b1ff20e20c and later · before 45085686b9559bfbe3a4f41d3d695a520668f5e1affected · git
    • c7741d16a57cbf97eebe53f27e8216b1ff20e20c and later · before 2ab9a19d896f5a0dd386e1f001c5309bc35f433baffected · git
    • c7741d16a57cbf97eebe53f27e8216b1ff20e20c and later · before dd594cdc24f2e48dab441732e6dfcafd6b0711d1affected · git
    • c7741d16a57cbf97eebe53f27e8216b1ff20e20c and later · before 2449007d3f73b2842c9734f45f0aadb522daf592affected · git
    • before 4.0not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.24.1.el9_47.3.0-427.24.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4

+96

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-26798Apr 4, 2024 · fbcon: always restore the old font data in fbcon_do_set_font()
    22Monitor
  • ← EarlierCVE-2024-26800Apr 4, 2024 · tls: fix use-after-free on failed backlog decryption
    31Monitor
  • Later →CVE-2024-26802Apr 4, 2024 · stmmac: Clear variable when destroying workqueue
    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 Linux2449007d3f73b2842c9734f45f0aadb522daf592Vendor (CNA)
Linux Linux2ab9a19d896f5a0dd386e1f001c5309bc35f433bVendor (CNA)
Linux Linux45085686b9559bfbe3a4f41d3d695a520668f5e1Vendor (CNA)
Linux Linux6dd0a9dfa99f8990a08eb8fdd8e79bee31c7d8e2Vendor (CNA)
Linux Linux98fb98fd37e42fd4ce13ff657ea64503e24b6090Vendor (CNA)
Linux Linuxda4569d450b193e39e87119fd316c0291b585d14Vendor (CNA)
Linux Linuxdd594cdc24f2e48dab441732e6dfcafd6b0711d1Vendor (CNA)
Linux Linuxe0b278650f07acf2e0932149183458468a731c03Vendor (CNA)
almalinux:bpftool7.3.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.82-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.24.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.24.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.24.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.24.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.24.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.24.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.24.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.24.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.24.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+8

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.

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.

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
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:N/I:N/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.

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

All records