Security readout for executives and security teams
Plain-English summary
A Linux Bluetooth driver flaw can crash the operating system when an affected MediaTek USB Bluetooth device disconnects. The issue is local rather than remotely reachable and mainly threatens availability. A crash could interrupt endpoint, appliance, or embedded-system operations and may cause data loss associated with an unexpected restart.
Executive priority
Treat this as a targeted high-priority availability issue, not an internet-wide emergency. Expedite remediation for operationally critical Linux systems using MediaTek USB Bluetooth, especially unattended appliances and embedded devices. Normal patch cycles may be appropriate where the affected hardware or disconnect condition is absent.
Technical view
The MediaTek path in Linux btusb claimed a special USB interrupt interface for ISO traffic but did not release it before unregistering the HCI device. Disconnecting the USB device could therefore cause a kernel panic during HCI teardown. The issue is classified as CWE-404 and scored CVSS 3.1 7.8 with local, low-complexity, low-privilege access.
Likely exposure
Exposure requires Linux systems using the affected MediaTek btusb functionality and a relevant USB disconnect event. The bundle identifies Linux versions including 6.11, 6.12.8, and 6.13, but its flattened version data does not define precise affected ranges. Confirm exposure against distribution advisories and applied kernel commits.
Exploitation context
The supplied CVSS vector describes a local, low-complexity condition requiring low privileges and no user interaction. Physical removal is an identified trigger. The bundle does not establish remote reachability, public exploitation, or active exploitation, and the CVE is not listed as KEV.
Researcher notes
The documented failure is improper interface cleanup during USB disconnect and HCI unregistration. Although the CVSS vector assigns high confidentiality, integrity, and availability impacts, the supplied description specifically demonstrates kernel panic; it does not explain data disclosure or modification. Exact vulnerable and fixed version boundaries remain unclear from the provided version data.
Mitigation direction
- Install a distribution-supported kernel containing the applicable interface-release fix.
- Check Linux vendor guidance for corrected package versions and backports.
- Prioritize systems where MediaTek USB Bluetooth devices are frequently disconnected.
- Restrict unnecessary physical or local access until affected systems are updated.
Validation and detection
- Inventory Linux kernel versions and connected MediaTek USB Bluetooth hardware.
- Compare installed kernel packages with distribution advisories and the cited stable commits.
- Review kernel logs for panic events associated with btusb or HCI device removal.
- Validate disconnect behavior only in a controlled, recoverable test environment after updating.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-404: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-56757 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/cc569d791ab2a0de74f76e470515d25d24c9b84bCVE reference, Linux
- https://git.kernel.org/stable/c/489304e67087abddc2666c5af0159cb95afdcf59CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Resource Shutdown or Release
Improper Resource Shutdown or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.