<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 13:40:38 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-43455</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-43455</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://127.0.0.1:10001/vuln/bell-cve-2026-43455</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0782 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0782</link>
      <description>certfr-2026-avi-0782</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0782</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43455</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43455</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 141 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mctp: route: hold key-&amp;gt;lock in mctp_flow_prepare_output() mctp_flow_prepare_output() checks key-&amp;gt;dev and may call mctp_dev_set_key(), but it does not hold key-&amp;gt;lock while doing so. mctp_dev_set_key() and mctp_dev_release_key() are annotated with __must_hold(&amp;amp;key-&amp;gt;lock), so key-&amp;gt;dev access is intended to be serialized by key-&amp;gt;lock. The mctp_sendmsg() transmit path reaches mctp_flow_prepare_output() via mctp_local_output() -&amp;gt; mctp_dst_output() without holding key-&amp;gt;lock, so the check-and-set sequence is racy. Example interleaving:   CPU0                                  CPU1   ----                                  ----   mctp_flow_prepare_output(key, devA)     if (!key-&amp;gt;dev)  // sees NULL                                         mctp_flow_prepare_output(                                             key, devB)                                           if (!key-&amp;gt;dev)  // still NULL                                           mctp_dev_set_key(devB, key)                                             mctp_dev_hold(devB)                                             key-&amp;gt;dev = devB     mctp_dev_set_key(devA, key)       mctp_dev_hold(devA)       key-&amp;gt;dev = devA   // overwrites devB Now both devA and devB references were acquired, but only the final key-&amp;gt;dev value is tracked for release. One reference can be lost, causing a resource leak as mctp_dev_release_key() would only decrease the reference on one dev. Fix by taking key-…&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 141 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mctp: route: hold key-&amp;gt;lock in mctp_flow_prepare_output() mctp_flow_prepare_output() checks key-&amp;gt;dev and may call mctp_dev_set_key(), but it does not hold key-&amp;gt;lock while doing so. mctp_dev_set_key() and mctp_dev_release_key() are annotated with __must_hold(&amp;amp;key-&amp;gt;lock), so key-&amp;gt;dev access is intended to be serialized by key-&amp;gt;lock. The mctp_sendmsg() transmit path reaches mctp_flow_prepare_output() via mctp_local_output() -&amp;gt; mctp_dst_output() without holding key-&amp;gt;lock, so the check-and-set sequence is racy. Example interleaving:   CPU0                                  CPU1   ----                                  ----   mctp_flow_prepare_output(key, devA)     if (!key-&amp;gt;dev)  // sees NULL                                         mctp_flow_prepare_output(                                             key, devB)                                           if (!key-&amp;gt;dev)  // still NULL                                           mctp_dev_set_key(devB, key)                                             mctp_dev_hold(devB)                                             key-&amp;gt;dev = devB     mctp_dev_set_key(devA, key)       mctp_dev_hold(devA)       key-&amp;gt;dev = devA   // overwrites devB Now both devA and devB references were acquired, but only the final key-&amp;gt;dev value is tracked for release. One reference can be lost, causing a resource leak as mctp_dev_release_key() would only decrease the reference on one dev. Fix by taking key-…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43455</guid>
    </item>
  </channel>
</rss>
