<?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>Thu, 19 Nov 2026 17:59:23 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64542</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64542</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-64542</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0981 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0981</link>
      <description>certfr-2026-avi-0981</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0981</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64542</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64542</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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv6: ndisc: fix NULL deref in accept_untracked_na() accept_untracked_na() re-fetches the inet6_dev with __in6_dev_get(dev) and dereferences idev-&amp;gt;cnf.accept_untracked_na without a NULL check, even though its only caller ndisc_recv_na() already fetched and NULL-checked idev for the same device. Both reads of dev-&amp;gt;ip6_ptr run in the same RCU read-side critical section, but a concurrent addrconf_ifdown() can clear dev-&amp;gt;ip6_ptr between them: lowering the MTU below IPV6_MIN_MTU calls addrconf_ifdown() without the synchronize_net() that orders the unregister path, so the re-fetch returns NULL and oopses:  BUG: KASAN: null-ptr-deref in ndisc_recv_na (net/ipv6/ndisc.c:974)  Read of size 4 at addr 0000000000000364  Call Trace:   &amp;lt;IRQ&amp;gt;   ndisc_recv_na (net/ipv6/ndisc.c:974)   icmpv6_rcv (net/ipv6/icmp.c:1193)   ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:479)   ip6_input_finish (net/ipv6/ip6_input.c:534)   ip6_input (net/ipv6/ip6_input.c:545)   ip6_mc_input (net/ipv6/ip6_input.c:635)   ipv6_rcv (net/ipv6/ip6_input.c:351)   &amp;lt;/IRQ&amp;gt; It is reachable by an unprivileged user via a network namespace. Pass the caller&amp;#39;s already validated idev instead of re-fetching it; the idev stays alive for the whole RCU critical section, so it is safe even after dev-&amp;gt;ip6_ptr has been cleared.&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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv6: ndisc: fix NULL deref in accept_untracked_na() accept_untracked_na() re-fetches the inet6_dev with __in6_dev_get(dev) and dereferences idev-&amp;gt;cnf.accept_untracked_na without a NULL check, even though its only caller ndisc_recv_na() already fetched and NULL-checked idev for the same device. Both reads of dev-&amp;gt;ip6_ptr run in the same RCU read-side critical section, but a concurrent addrconf_ifdown() can clear dev-&amp;gt;ip6_ptr between them: lowering the MTU below IPV6_MIN_MTU calls addrconf_ifdown() without the synchronize_net() that orders the unregister path, so the re-fetch returns NULL and oopses:  BUG: KASAN: null-ptr-deref in ndisc_recv_na (net/ipv6/ndisc.c:974)  Read of size 4 at addr 0000000000000364  Call Trace:   &amp;lt;IRQ&amp;gt;   ndisc_recv_na (net/ipv6/ndisc.c:974)   icmpv6_rcv (net/ipv6/icmp.c:1193)   ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:479)   ip6_input_finish (net/ipv6/ip6_input.c:534)   ip6_input (net/ipv6/ip6_input.c:545)   ip6_mc_input (net/ipv6/ip6_input.c:635)   ipv6_rcv (net/ipv6/ip6_input.c:351)   &amp;lt;/IRQ&amp;gt; It is reachable by an unprivileged user via a network namespace. Pass the caller&amp;#39;s already validated idev instead of re-fetching it; the idev stays alive for the whole RCU critical section, so it is safe even after dev-&amp;gt;ip6_ptr has been cleared.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64542</guid>
    </item>
  </channel>
</rss>
