CVE-2026-43069

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.

Is your site exposed to CVE-2026-43069?

Run a free security scan — no signup, results in seconds.

EPSS — Exploit Prediction

0.0001

Probability of exploitation

0.02%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

References

Other References

https://git.kernel.org/stable/c/28904375d54b436a757641fb0331537778c0de5a https://git.kernel.org/stable/c/31148a7be723aa9f2e8fbd62424825ab8d577973 https://git.kernel.org/stable/c/5213ef54528dd1ac79b846e30d8f72ce092794aa https://git.kernel.org/stable/c/95e8601af227b2b4390eecf8db6abdb9f6a91f17 https://git.kernel.org/stable/c/9ecbfd93cd6de6c78cb7fd51fe079e36c7ff074b https://git.kernel.org/stable/c/a7803df606a7d22e896b030f619e1d9d20ae0c6b https://git.kernel.org/stable/c/b2dfbf1b5ff192cefd49574b951a4af9ddd32213 https://git.kernel.org/stable/c/e6d95488c8c964d1df0d3e1db44c958706311e86

Frequently Asked Questions

What is CVE-2026-43069? +

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.

How do I check if I'm vulnerable to CVE-2026-43069? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.