Security readout for executives and security teams
Plain-English summary
A Linux Bluetooth driver flaw can access memory after it has been released while processing MediaTek controller crash data. This can destabilize affected systems and may threaten confidentiality, integrity, and availability. Risk is limited to systems using the relevant MediaTek Bluetooth path, but the supplied CVSS score is 8.8.
Executive priority
Treat as a high-priority platform update for fleets using MediaTek Bluetooth, especially exposed endpoints and appliances. First determine whether btmtk is actually used; unaffected hardware materially lowers urgency. Patch through supported kernel or distribution channels. There is no supplied evidence of active exploitation, so emergency incident response is not justified solely by this bundle.
Technical view
CVE-2024-56653 is a CWE-416 use-after-free in btmtk_process_coredump. hci_devcd_append may release the socket buffer, yet the function subsequently accesses it. KASAN reproduced the invalid read in the btusb receive workqueue. The correction completes coredump processing at the proper counter boundary by checking greater-than-or-equal rather than greater-than.
Likely exposure
Likely exposure is Linux systems using the btmtk MediaTek Bluetooth driver and vulnerable kernel builds. The bundle identifies affected 6.6-era through 6.13 version data, but its flattened version list does not establish precise ranges. Distribution backports may change exposure, so package-level vendor advisories and fix-commit presence must be checked.
Exploitation context
The CVSS vector describes adjacent-network reachability, low complexity, no privileges, and no user interaction. However, the supplied sources provide no public exploitation evidence, and the CVE is not listed as KEV. The demonstrated evidence is a KASAN-detected kernel use-after-free; practical exploitability and reliable impact beyond crashing are not established here.
Researcher notes
The report shows a 232-byte sk_buff freed through hci_devcd_rx and later read in btmtk_process_coredump. The root condition is lifetime invalidation after hci_devcd_append. The stated boundary correction changes the completion test from cnt greater than MTK_COREDUMP_NUM to greater-than-or-equal. Exact vulnerable ranges and exploit primitives require further vendor-specific analysis.
Mitigation direction
- Update to a supported vendor kernel containing the applicable referenced stable fix.
- Check distribution advisories because vendors may backport fixes without changing to an upstream version.
- Prioritize systems with MediaTek Bluetooth hardware or the btmtk module active.
- Follow vendor guidance for temporary exposure reduction if an immediate kernel update is unavailable.
Validation and detection
- Inventory kernel package versions and identify systems using MediaTek Bluetooth hardware.
- Confirm whether the btmtk module is present, loaded, or exercised by attached hardware.
- Compare vendor kernel changelogs or source against the three referenced stable commits.
- After updating, verify the running kernel matches the patched package and Bluetooth remains operational.
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-416: 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-56653 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
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/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:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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
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/ecdcaea0e4057171ea4c3783e1cc1c900ad99125CVE reference, Linux
- https://git.kernel.org/stable/c/d20ff1d3cb40479789368f502eedb0a00e4161fcCVE reference, Linux
- https://git.kernel.org/stable/c/b548f5e9456c568155499d9ebac675c0d7a296e8CVE 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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.