Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2024-26801

8.8 · HIGH

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…

Published Apr 4, 2024CWE-416EPSS 0.43%

Overview

CVE-2024-26801 is a high-severity vulnerability. It was published on April 4, 2024 and has a CVSS 3.1 base score of 8.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/2449007d3f73b2842c9734f45f0aadb522daf592Refgit.kernel.org/stable/c/2ab9a19d896f5a0dd386e1f001c5309bc35f433bRefgit.kernel.org/stable/c/45085686b9559bfbe3a4f41d3d695a520668f5e1Refgit.kernel.org/stable/c/6dd0a9dfa99f8990a08eb8fdd8e79bee31c7d8e2Refgit.kernel.org/stable/c/98fb98fd37e42fd4ce13ff657ea64503e24b6090Refgit.kernel.org/stable/c/da4569d450b193e39e87119fd316c0291b585d14Refgit.kernel.org/stable/c/dd594cdc24f2e48dab441732e6dfcafd6b0711d1Refgit.kernel.org/stable/c/e0b278650f07acf2e0932149183458468a731c03Refgit.kernel.org/stable/c/2449007d3f73b2842c9734f45f0aadb522daf592Refgit.kernel.org/stable/c/2ab9a19d896f5a0dd386e1f001c5309bc35f433b

How CyberStrike helps

Frequently asked questions

What is CVE-2024-26801?

CVE-2024-26801 is a high-severity vulnerability. It was published on April 4, 2024 and has a CVSS 3.1 base score of 8.8 (HIGH).

How severe is CVE-2024-26801?

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2024-26801?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2024-26801?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2024-26801 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2024

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999