CVE record · CVE-2024-26887

Bluetooth: btusb: Fix memory leak

No CVSS scoreEPSS 0.0022 · 12th percentile

Published by the CVE Program (CNA: Linux) at 17 Apr 2024, 10:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

Affected products, as the CNA wrote them
VendorProductVersions
Linux Linux
  • affected 0b70151328781a89c89e4cf3fae21fc0e98d869e to before 620b9e60e4b55fa55540ce852a0f3c9e6091dbbc git
  • affected 0b70151328781a89c89e4cf3fae21fc0e98d869e to before b10e6f6b160a60b98fb7476028f5a95405bbd725 git
  • affected 0b70151328781a89c89e4cf3fae21fc0e98d869e to before b08bd8f02a24e2b82fece5ac51dc1c3d9aa6c404 git
  • affected 0b70151328781a89c89e4cf3fae21fc0e98d869e to before 79f4127a502c5905f04da1f20a7bbe07103fb77c git
Other versions: unaffected
Linux Linux
  • affected 6.6
  • unaffected before 6.6 semver
  • unaffected 6.6.23 to 6.6.*, inclusive semver
  • unaffected 6.7.11 to 6.7.*, inclusive semver
  • unaffected 6.8.2 to 6.8.*, inclusive semver
  • unaffected 6.9 to *, inclusive original_commit_for_fix
Other versions: affected
Identifiers
CVE-2024-26887
CNA
Linux
Published
17 Apr 2024
Updated
11 May 2026

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS 0.0022, the 12th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the CVE Program, published 17 Apr 2024. New records show when each source confirmed them.

Sources

References from the CNA

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.