LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26887: Bluetooth: btusb: Fix memory leak

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: Fix memory leak This checks if CONFIG_DEV_COREDUMP is enabled before attempting to clone the skb and also make sure btmtk_process_coredump frees the skb passed following the same logic.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26887 is a Linux kernel Bluetooth driver memory leak. The public record describes a missing allocation/freeing guard around Bluetooth device coredump handling. Business urgency is limited unless affected Linux systems rely on Bluetooth hardware, but kernel memory leaks can degrade stability if repeatedly triggered.

Executive priority

Handle through normal kernel patch management unless Bluetooth-heavy fleets, kiosks, laptops, or embedded Linux devices are operationally important. Escalate if vendor guidance later confirms remote or low-privilege triggerability.

Technical view

The issue is in the Linux kernel btusb Bluetooth driver. The fix checks CONFIG_DEV_COREDUMP before cloning an skb and ensures btmtk_process_coredump frees the skb using matching logic. No CVSS, CWE, trigger conditions, privilege requirements, or exploit details are provided in the source bundle.

Likely exposure

Exposure appears limited to Linux kernels containing the affected btusb Bluetooth coredump logic, with listed affected/fixed version markers around 6.6, 6.6.23, 6.7.11, 6.8.2, and 6.9. Systems without relevant Bluetooth USB driver use are less likely to be exposed.

Exploitation context

The source bundle does not show active exploitation, public exploit availability, or CISA KEV listing. It also does not describe a practical attack path. Treat this as a kernel stability and potential denial-of-service concern until vendor advisories clarify reachability.

Researcher notes

The record is sparse: no CVSS, CWE, exploit status, or reproducer is provided. The key technical clues are skb clone/free handling, CONFIG_DEV_COREDUMP gating, and btmtk_process_coredump cleanup. Review the referenced stable commits and downstream distro backports for exact affected ranges.

Mitigation direction

  • Check Linux distribution advisories for CVE-2024-26887 package status.
  • Update affected kernels to a vendor release containing the referenced stable fixes.
  • Prioritize systems with enabled Bluetooth USB hardware or btusb driver use.
  • If updates are delayed, review vendor guidance for temporary Bluetooth mitigation options.

Validation and detection

  • Inventory Linux kernel versions across managed endpoints and servers.
  • Identify systems loading or depending on the btusb Bluetooth driver.
  • Confirm vendor kernel changelogs include the CVE-2024-26887 fixes.
  • Monitor affected systems for kernel memory pressure or Bluetooth driver instability.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2024-26887 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0b70151328781a89c89e4cf3fae21fc0e98d869e, 0b70151328781a89c89e4cf3fae21fc0e98d869e, 0b70151328781a89c89e4cf3fae21fc0e98d869e, 0b70151328781a89c89e4cf3fae21fc0e98d869eunaffected
LinuxLinux6.6, 0, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.