<?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 12:43:51 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74562</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-74562</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-74562</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1469 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1469</link>
      <description>certfr-2026-avi-1469</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1469</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74562</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74562</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nexthop: take nh-&amp;gt;lock for f6i_list walks in replace check and notify fib6_check_nh_list() and __nexthop_replace_notify() walk nh-&amp;gt;f6i_list during an RTNL-serialized nexthop replace without holding nh-&amp;gt;lock. IPv6 RTM_NEWROUTE/RTM_DELROUTE run without RTNL and mutate that list under nh-&amp;gt;lock (fib6_add_rt2node_nh(), fib6_purge_rt()), so both walks race a concurrent route delete that unlinks and frees a fib6_info:   BUG: KASAN: slab-use-after-free in rt6_fill_node.isra.0 (net/ipv6/route.c:5799)   Read of size 4 at addr ffff888014607e64 by task exploit/143    rt6_fill_node.isra.0 (net/ipv6/route.c:5799)    fib6_rt_update (net/ipv6/route.c:6412)    __nexthop_replace_notify (net/ipv4/nexthop.c:2542)    rtm_new_nexthop (net/ipv4/nexthop.c:2554)    rtnetlink_rcv_msg (net/core/rtnetlink.c:7076)   BUG: KASAN: slab-use-after-free in fib6_check_nh_list (net/ipv4/nexthop.c:1605)   Read of size 8 at addr ffff888014a7d068 by task exploit/142    fib6_check_nh_list (net/ipv4/nexthop.c:1605)    rtm_new_nexthop (net/ipv4/nexthop.c:2575)    rtnetlink_rcv_msg (net/core/rtnetlink.c:7076) Both walks only read the entries and take no tb6_lock, so protect them with nh-&amp;gt;lock; fib6_rt_update() uses gfp_any(), which returns GFP_ATOMIC under the lock.&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nexthop: take nh-&amp;gt;lock for f6i_list walks in replace check and notify fib6_check_nh_list() and __nexthop_replace_notify() walk nh-&amp;gt;f6i_list during an RTNL-serialized nexthop replace without holding nh-&amp;gt;lock. IPv6 RTM_NEWROUTE/RTM_DELROUTE run without RTNL and mutate that list under nh-&amp;gt;lock (fib6_add_rt2node_nh(), fib6_purge_rt()), so both walks race a concurrent route delete that unlinks and frees a fib6_info:   BUG: KASAN: slab-use-after-free in rt6_fill_node.isra.0 (net/ipv6/route.c:5799)   Read of size 4 at addr ffff888014607e64 by task exploit/143    rt6_fill_node.isra.0 (net/ipv6/route.c:5799)    fib6_rt_update (net/ipv6/route.c:6412)    __nexthop_replace_notify (net/ipv4/nexthop.c:2542)    rtm_new_nexthop (net/ipv4/nexthop.c:2554)    rtnetlink_rcv_msg (net/core/rtnetlink.c:7076)   BUG: KASAN: slab-use-after-free in fib6_check_nh_list (net/ipv4/nexthop.c:1605)   Read of size 8 at addr ffff888014a7d068 by task exploit/142    fib6_check_nh_list (net/ipv4/nexthop.c:1605)    rtm_new_nexthop (net/ipv4/nexthop.c:2575)    rtnetlink_rcv_msg (net/core/rtnetlink.c:7076) Both walks only read the entries and take no tb6_lock, so protect them with nh-&amp;gt;lock; fib6_rt_update() uses gfp_any(), which returns GFP_ATOMIC under the lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74562</guid>
    </item>
  </channel>
</rss>
