<?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>Mon, 28 Sep 2026 16:55:14 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-97907</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-97907</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: btrtl: Don&amp;#39;t leak return code when parsing firmware format v2&lt;/p&gt;
&lt;p&gt;When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally
ignores all security headers. However, the implementation simply breaks
from a switch statement and leaks uninitialized return code `rc&amp;#39; (if the
first section is a security one) or the previous section&amp;#39;s `rc&amp;#39;.&lt;/p&gt;
&lt;p&gt;Fix it by really skipping a loop with `continue&amp;#39;. For consistency and
readability, also do the same for the default case.&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: btrtl: Don&amp;#39;t leak return code when parsing firmware format v2&lt;/p&gt;
&lt;p&gt;When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally
ignores all security headers. However, the implementation simply breaks
from a switch statement and leaks uninitialized return code `rc&amp;#39; (if the
first section is a security one) or the previous section&amp;#39;s `rc&amp;#39;.&lt;/p&gt;
&lt;p&gt;Fix it by really skipping a loop with `continue&amp;#39;. For consistency and
readability, also do the same for the default case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-97907</guid>
    </item>
    <item>
      <title>GHSA-cc6q-p4xg-qp8m</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-cc6q-p4xg-qp8m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: btrtl: Don&amp;#39;t leak return code when parsing firmware format v2&lt;/p&gt;
&lt;p&gt;When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally
ignores all security headers. However, the implementation simply breaks
from a switch statement and leaks uninitialized return code `rc&amp;#39; (if the
first section is a security one) or the previous section&amp;#39;s `rc&amp;#39;.&lt;/p&gt;
&lt;p&gt;Fix it by really skipping a loop with `continue&amp;#39;. For consistency and
readability, also do the same for the default case.&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: btrtl: Don&amp;#39;t leak return code when parsing firmware format v2&lt;/p&gt;
&lt;p&gt;When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally
ignores all security headers. However, the implementation simply breaks
from a switch statement and leaks uninitialized return code `rc&amp;#39; (if the
first section is a security one) or the previous section&amp;#39;s `rc&amp;#39;.&lt;/p&gt;
&lt;p&gt;Fix it by really skipping a loop with `continue&amp;#39;. For consistency and
readability, also do the same for the default case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-cc6q-p4xg-qp8m</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-97907</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97907</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: Don&amp;#39;t leak return code when parsing firmware format v2 When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally ignores all security headers. However, the implementation simply breaks from a switch statement and leaks uninitialized return code `rc&amp;#39; (if the first section is a security one) or the previous section&amp;#39;s `rc&amp;#39;. Fix it by really skipping a loop with `continue&amp;#39;. For consistency and readability, also do the same for the default case.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: Don&amp;#39;t leak return code when parsing firmware format v2 When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally ignores all security headers. However, the implementation simply breaks from a switch statement and leaks uninitialized return code `rc&amp;#39; (if the first section is a security one) or the previous section&amp;#39;s `rc&amp;#39;. Fix it by really skipping a loop with `continue&amp;#39;. For consistency and readability, also do the same for the default case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97907</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
