<?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:49:49 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-43086</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-43086</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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: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-43086</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0864 — 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-0864</link>
      <description>certfr-2026-avi-0864</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0864</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43086</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43086</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 142 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipvs: fix NULL deref in ip_vs_add_service error path When ip_vs_bind_scheduler() succeeds in ip_vs_add_service(), the local variable sched is set to NULL.  If ip_vs_start_estimator() subsequently fails, the out_err cleanup calls ip_vs_unbind_scheduler(svc, sched) with sched == NULL.  ip_vs_unbind_scheduler() passes the cur_sched NULL check (because svc-&amp;gt;scheduler was set by the successful bind) but then dereferences the NULL sched parameter at sched-&amp;gt;done_service, causing a kernel panic at offset 0x30 from NULL.  Oops: general protection fault, [..] [#1] PREEMPT SMP KASAN NOPTI  KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]  RIP: 0010:ip_vs_unbind_scheduler (net/netfilter/ipvs/ip_vs_sched.c:69)  Call Trace:   &amp;lt;TASK&amp;gt;   ip_vs_add_service.isra.0 (net/netfilter/ipvs/ip_vs_ctl.c:1500)   do_ip_vs_set_ctl (net/netfilter/ipvs/ip_vs_ctl.c:2809)   nf_setsockopt (net/netfilter/nf_sockopt.c:102)   [..] Fix by simply not clearing the local sched variable after a successful bind.  ip_vs_unbind_scheduler() already detects whether a scheduler is installed via svc-&amp;gt;scheduler, and keeping sched non-NULL ensures the error path passes the correct pointer to both ip_vs_unbind_scheduler() and ip_vs_scheduler_put(). While the bug is older, the problem popups in more recent kernels (6.2), when the new error path is taken after the ip_vs_start_estimator() call.&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 142 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipvs: fix NULL deref in ip_vs_add_service error path When ip_vs_bind_scheduler() succeeds in ip_vs_add_service(), the local variable sched is set to NULL.  If ip_vs_start_estimator() subsequently fails, the out_err cleanup calls ip_vs_unbind_scheduler(svc, sched) with sched == NULL.  ip_vs_unbind_scheduler() passes the cur_sched NULL check (because svc-&amp;gt;scheduler was set by the successful bind) but then dereferences the NULL sched parameter at sched-&amp;gt;done_service, causing a kernel panic at offset 0x30 from NULL.  Oops: general protection fault, [..] [#1] PREEMPT SMP KASAN NOPTI  KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]  RIP: 0010:ip_vs_unbind_scheduler (net/netfilter/ipvs/ip_vs_sched.c:69)  Call Trace:   &amp;lt;TASK&amp;gt;   ip_vs_add_service.isra.0 (net/netfilter/ipvs/ip_vs_ctl.c:1500)   do_ip_vs_set_ctl (net/netfilter/ipvs/ip_vs_ctl.c:2809)   nf_setsockopt (net/netfilter/nf_sockopt.c:102)   [..] Fix by simply not clearing the local sched variable after a successful bind.  ip_vs_unbind_scheduler() already detects whether a scheduler is installed via svc-&amp;gt;scheduler, and keeping sched non-NULL ensures the error path passes the correct pointer to both ip_vs_unbind_scheduler() and ip_vs_scheduler_put(). While the bug is older, the problem popups in more recent kernels (6.2), when the new error path is taken after the ip_vs_start_estimator() call.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43086</guid>
    </item>
  </channel>
</rss>
