<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 15:14:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43069 — Bluetooth: hci_ll: Fix firmware leak on error path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43069</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_ll: Fix firmware leak on error path&lt;/p&gt;
&lt;p&gt;Smatch reports:&lt;/p&gt;
&lt;p&gt;drivers/bluetooth/hci_ll.c:587 download_firmware() warn:
&amp;#39;fw&amp;#39; from request_firmware() not released on lines: 544.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Fix this by calling release_firmware() before returning when
request_firmware() succeeded but the firmware content is invalid.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_ll: Fix firmware leak on error path&lt;/p&gt;
&lt;p&gt;Smatch reports:&lt;/p&gt;
&lt;p&gt;drivers/bluetooth/hci_ll.c:587 download_firmware() warn:
&amp;#39;fw&amp;#39; from request_firmware() not released on lines: 544.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Fix this by calling release_firmware() before returning when
request_firmware() succeeded but the firmware content is invalid.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43069</guid>
    </item>
  </channel>
</rss>
