<?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 09:53:27 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-90257</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-90257</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-90257</guid>
    </item>
    <item>
      <title>fkie_cve-2026-90257</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-90257</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: virtio_bt: avoid OOB read of build info string&lt;/p&gt;
&lt;p&gt;The virtbt_setup_zephyr() sends the Zephyr vendor command 0xfc08 (Read
Build Information) and hands 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. A backend that answers with status only leaves that
pointer past the end of the received data, so the walk reads adjacent
slab memory until it meets a NUL. Those bytes reach the kernel log and
the firmware-info debugfs file.&lt;/p&gt;
&lt;p&gt;To fix this, print the string with a bounded &amp;#34;%.*s&amp;#34; limited to
skb-&amp;gt;len - 1. A short or unterminated response then prints as much as
arrived instead of failing setup.&lt;/p&gt;
&lt;p&gt;This mirrors commit dd068ef04412 (&amp;#34;Bluetooth: bpa10x: avoid OOB read of
revision string in bpa10x_setup()&amp;#34;), which fixed the identical pattern.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: virtio_bt: avoid OOB read of build info string&lt;/p&gt;
&lt;p&gt;The virtbt_setup_zephyr() sends the Zephyr vendor command 0xfc08 (Read
Build Information) and hands 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. A backend that answers with status only leaves that
pointer past the end of the received data, so the walk reads adjacent
slab memory until it meets a NUL. Those bytes reach the kernel log and
the firmware-info debugfs file.&lt;/p&gt;
&lt;p&gt;To fix this, print the string with a bounded &amp;#34;%.*s&amp;#34; limited to
skb-&amp;gt;len - 1. A short or unterminated response then prints as much as
arrived instead of failing setup.&lt;/p&gt;
&lt;p&gt;This mirrors commit dd068ef04412 (&amp;#34;Bluetooth: bpa10x: avoid OOB read of
revision string in bpa10x_setup()&amp;#34;), which fixed the identical pattern.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-90257</guid>
    </item>
    <item>
      <title>GHSA-jc9v-mfxc-m9mm</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-jc9v-mfxc-m9mm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: virtio_bt: avoid OOB read of build info string&lt;/p&gt;
&lt;p&gt;The virtbt_setup_zephyr() sends the Zephyr vendor command 0xfc08 (Read
Build Information) and hands 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. A backend that answers with status only leaves that
pointer past the end of the received data, so the walk reads adjacent
slab memory until it meets a NUL. Those bytes reach the kernel log and
the firmware-info debugfs file.&lt;/p&gt;
&lt;p&gt;To fix this, print the string with a bounded &amp;#34;%.*s&amp;#34; limited to
skb-&amp;gt;len - 1. A short or unterminated response then prints as much as
arrived instead of failing setup.&lt;/p&gt;
&lt;p&gt;This mirrors commit dd068ef04412 (&amp;#34;Bluetooth: bpa10x: avoid OOB read of
revision string in bpa10x_setup()&amp;#34;), which fixed the identical pattern.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: virtio_bt: avoid OOB read of build info string&lt;/p&gt;
&lt;p&gt;The virtbt_setup_zephyr() sends the Zephyr vendor command 0xfc08 (Read
Build Information) and hands 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. A backend that answers with status only leaves that
pointer past the end of the received data, so the walk reads adjacent
slab memory until it meets a NUL. Those bytes reach the kernel log and
the firmware-info debugfs file.&lt;/p&gt;
&lt;p&gt;To fix this, print the string with a bounded &amp;#34;%.*s&amp;#34; limited to
skb-&amp;gt;len - 1. A short or unterminated response then prints as much as
arrived instead of failing setup.&lt;/p&gt;
&lt;p&gt;This mirrors commit dd068ef04412 (&amp;#34;Bluetooth: bpa10x: avoid OOB read of
revision string in bpa10x_setup()&amp;#34;), which fixed the identical pattern.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-jc9v-mfxc-m9mm</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-90257</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90257</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: virtio_bt: avoid OOB read of build info string The virtbt_setup_zephyr() sends the Zephyr vendor command 0xfc08 (Read Build Information) and hands 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. A backend that answers with status only leaves that pointer past the end of the received data, so the walk reads adjacent slab memory until it meets a NUL. Those bytes reach the kernel log and the firmware-info debugfs file. To fix this, print the string with a bounded &amp;#34;%.*s&amp;#34; limited to skb-&amp;gt;len - 1. A short or unterminated response then prints as much as arrived instead of failing setup. This mirrors commit dd068ef04412 (&amp;#34;Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup()&amp;#34;), which fixed the identical pattern.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: virtio_bt: avoid OOB read of build info string The virtbt_setup_zephyr() sends the Zephyr vendor command 0xfc08 (Read Build Information) and hands 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. A backend that answers with status only leaves that pointer past the end of the received data, so the walk reads adjacent slab memory until it meets a NUL. Those bytes reach the kernel log and the firmware-info debugfs file. To fix this, print the string with a bounded &amp;#34;%.*s&amp;#34; limited to skb-&amp;gt;len - 1. A short or unterminated response then prints as much as arrived instead of failing setup. This mirrors commit dd068ef04412 (&amp;#34;Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup()&amp;#34;), which fixed the identical pattern.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90257</guid>
    </item>
  </channel>
</rss>
