Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43069Bluetooth: hci_ll: Fix firmware leak on error path

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_ll: Fix firmware leak on error path Smatch reports: drivers/bluetooth/hci_ll.c:587 download_firmware() warn: 'fw' from request_firmware() not released on lines: 544. In download_firmware(), if request_firmware() succeeds but the returned firmware content is invalid (no data or zero size), the function returns without releasing the firmware, resulting in a resource leak. Fix this by calling release_firmware() before returning when request_firmware() succeeded but the firmware content is invalid.

Timeline

  1. ID reserved

    By Linux

  2. · 4 days later

    Published

  3. · 6 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43069, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.11% · top 98% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 371805522f870986144fcd88727a47858e364a2c – < 95e8601af227b2b4390eecf8db6abdb9f6a91f17
    • affected 371805522f870986144fcd88727a47858e364a2c – < e6d95488c8c964d1df0d3e1db44c958706311e86
    • affected 371805522f870986144fcd88727a47858e364a2c – < b2dfbf1b5ff192cefd49574b951a4af9ddd32213
    • affected 371805522f870986144fcd88727a47858e364a2c – < 28904375d54b436a757641fb0331537778c0de5a
    • affected 371805522f870986144fcd88727a47858e364a2c – < 5213ef54528dd1ac79b846e30d8f72ce092794aa
    • affected 371805522f870986144fcd88727a47858e364a2c – < 9ecbfd93cd6de6c78cb7fd51fe079e36c7ff074b
    • affected 371805522f870986144fcd88727a47858e364a2c – < a7803df606a7d22e896b030f619e1d9d20ae0c6b
    • affected 371805522f870986144fcd88727a47858e364a2c – < 31148a7be723aa9f2e8fbd62424825ab8d577973
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.131 – ≤ 6.6.*
    • unaffected 6.12.80 – ≤ 6.12.*
    • unaffected 6.18.21 – ≤ 6.18.*
    • unaffected 6.19.11 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43069 badge
[![CVE-2026-43069](https://cveledger.app/badge/CVE-2026-43069.svg)](https://cveledger.app/cve/CVE-2026-43069)

Record last updated .