Bluetooth disruption via oversized BIG handle
Published Jul 30, 2024 · Updated Aug 5, 2026
Improper handle validation in the Linux kernel Bluetooth subsystem allows physically proximate attackers to disrupt Bluetooth through a BIG event. The hci_le_big_sync_established_evt path accepts a BIS handle above 0x0eff, creates a bogus unset hci_conn, and later releases an IDA identifier that was never allocated for that handle. An unpaired device in radio range can reach the path when the host is configured as a LE Audio or Auracast ISO sink; teardown triggers a kernel warning, which becomes a panic when panic_on_warn is enabled, and can also desynchronize Bluetooth connection state.
Summary
What happened
Improper handle validation in the Linux kernel Bluetooth subsystem allows physically proximate attackers to disrupt Bluetooth through a BIG event. The hci_le_big_sync_established_evt path accepts a BIS handle above 0x0eff, creates a bogus unset hci_conn, and later releases an IDA identifier that was never allocated for that handle. An unpaired device in radio range can reach the path when the host is configured as a LE Audio or Auracast ISO sink; teardown triggers a kernel warning, which becomes a panic when panic_on_warn is enabled, and can also desynchronize Bluetooth connection state.
The record
- CVE
- CVE-2024-42133
- Published
- Jul 30, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=181a42edddf51d5d9697ecdf365d72ebeab5afb0 <015d79c96d62cd8a4a359fcf5be40d58088c936b
- Affected versionversion=181a42edddf51d5d9697ecdf365d72ebeab5afb0 <dad0003ccc68457baf005a6ed75b4d321463fe3d
- Affected versionversion=6.5.12 <6.6
- Affected versionversion=6.6.2 <6.6.39
- Affected versionversion=6.7
- Affected versionversion=84cb0143fb8a03bf941c7aaedd56c938c99dafad <38263088b845abeeeb98dda5b87c0de3063b6dbb
- Affected versionversion=e9f708beada55426c8d678e2f46af659eb5bf4f0
- Affected versionversion=f7e83f2278f06b577e3c92ea2f4e8e8c6fc72a8f <a06a8cc80fa203fde828a8429583f7e4fe27eca4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- syzbot hci_conn_set_handle reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo