<?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>Tue, 29 Sep 2026 03:05:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64549 — Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64549</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: bpa10x: avoid OOB read of revision string in bpa10x_setup()&lt;/p&gt;
&lt;p&gt;bpa10x_setup() sends the vendor command 0xfc0e and passes the response
to bt_dev_info() and hci_set_fw_info() as a &amp;#34;%s&amp;#34; string starting at
skb-&amp;gt;data + 1, without checking the length:&lt;/p&gt;
&lt;p&gt;bt_dev_info(hdev, &amp;#34;%s&amp;#34;, (char *)(skb-&amp;gt;data + 1));
	hci_set_fw_info(hdev, &amp;#34;%s&amp;#34;, skb-&amp;gt;data + 1);&lt;/p&gt;
&lt;p&gt;A device that returns a one-byte response (status only) leaves
skb-&amp;gt;data + 1 past the end of the data, and the %s walk reads adjacent
slab memory until it meets a NUL. The same happens when the payload is
not NUL-terminated within skb-&amp;gt;len. The out-of-bounds bytes end up in
the kernel log and the firmware-info debugfs file.&lt;/p&gt;
&lt;p&gt;Print the revision string with a bounded &amp;#34;%.*s&amp;#34; limited to skb-&amp;gt;len - 1
instead. This keeps the string readable for well-behaved devices while
never reading past the received data, and does not fail setup, so a
device returning a short or unterminated response keeps working.&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: bpa10x: avoid OOB read of revision string in bpa10x_setup()&lt;/p&gt;
&lt;p&gt;bpa10x_setup() sends the vendor command 0xfc0e and passes the response
to bt_dev_info() and hci_set_fw_info() as a &amp;#34;%s&amp;#34; string starting at
skb-&amp;gt;data + 1, without checking the length:&lt;/p&gt;
&lt;p&gt;bt_dev_info(hdev, &amp;#34;%s&amp;#34;, (char *)(skb-&amp;gt;data + 1));
	hci_set_fw_info(hdev, &amp;#34;%s&amp;#34;, skb-&amp;gt;data + 1);&lt;/p&gt;
&lt;p&gt;A device that returns a one-byte response (status only) leaves
skb-&amp;gt;data + 1 past the end of the data, and the %s walk reads adjacent
slab memory until it meets a NUL. The same happens when the payload is
not NUL-terminated within skb-&amp;gt;len. The out-of-bounds bytes end up in
the kernel log and the firmware-info debugfs file.&lt;/p&gt;
&lt;p&gt;Print the revision string with a bounded &amp;#34;%.*s&amp;#34; limited to skb-&amp;gt;len - 1
instead. This keeps the string readable for well-behaved devices while
never reading past the received data, and does not fail setup, so a
device returning a short or unterminated response keeps working.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64549</guid>
    </item>
  </channel>
</rss>
