<?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 00:44:25 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-52941</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-52941</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-52941</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0812 — De multiples vulnérabilités ont été découvertes dans Microsoft Azure Linux. Elles permettent à un attaquant de provoque…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0812</link>
      <description>certfr-2026-avi-0812</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0812</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-52941</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-52941</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 163 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/smc: avoid NULL deref of conn-&amp;gt;lnk in smc_msg_event tracepoint The smc_msg_event tracepoint class, shared by smc_tx_sendmsg and smc_rx_recvmsg, unconditionally dereferences smc-&amp;gt;conn.lnk: 	__string(name, smc-&amp;gt;conn.lnk-&amp;gt;ibname) conn-&amp;gt;lnk is only set for SMC-R; for SMC-D it is NULL. Other code on these paths already handles this (e.g. !conn-&amp;gt;lnk in SMC_STAT_RMB_TX_SIZE_SMALL()). With the tracepoint enabled, the first sendmsg()/recvmsg() on an SMC-D socket crashes:   Oops: general protection fault, probably for non-canonical address   KASAN: null-ptr-deref in range [...]   RIP: 0010:strlen+0x1e/0xa0   Call Trace:    trace_event_raw_event_smc_msg_event (net/smc/smc_tracepoint.h:44)    smc_rx_recvmsg (net/smc/smc_rx.c:515)    smc_recvmsg (net/smc/af_smc.c:2859)    __sys_recvfrom (net/socket.c:2315)    __x64_sys_recvfrom (net/socket.c:2326)    do_syscall_64 The faulting address 0x3e0 is offsetof(struct smc_link, ibname), confirming the NULL -&amp;gt;lnk deref. Enabling the tracepoint requires root, but the trigger itself is unprivileged: socket(AF_SMC, ...) has no capability check, and SMC-D negotiation needs no admin step on s390 or on x86 with the loopback ISM device loaded. Log an empty device name for SMC-D instead of dereferencing NULL.&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 163 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/smc: avoid NULL deref of conn-&amp;gt;lnk in smc_msg_event tracepoint The smc_msg_event tracepoint class, shared by smc_tx_sendmsg and smc_rx_recvmsg, unconditionally dereferences smc-&amp;gt;conn.lnk: 	__string(name, smc-&amp;gt;conn.lnk-&amp;gt;ibname) conn-&amp;gt;lnk is only set for SMC-R; for SMC-D it is NULL. Other code on these paths already handles this (e.g. !conn-&amp;gt;lnk in SMC_STAT_RMB_TX_SIZE_SMALL()). With the tracepoint enabled, the first sendmsg()/recvmsg() on an SMC-D socket crashes:   Oops: general protection fault, probably for non-canonical address   KASAN: null-ptr-deref in range [...]   RIP: 0010:strlen+0x1e/0xa0   Call Trace:    trace_event_raw_event_smc_msg_event (net/smc/smc_tracepoint.h:44)    smc_rx_recvmsg (net/smc/smc_rx.c:515)    smc_recvmsg (net/smc/af_smc.c:2859)    __sys_recvfrom (net/socket.c:2315)    __x64_sys_recvfrom (net/socket.c:2326)    do_syscall_64 The faulting address 0x3e0 is offsetof(struct smc_link, ibname), confirming the NULL -&amp;gt;lnk deref. Enabling the tracepoint requires root, but the trigger itself is unprivileged: socket(AF_SMC, ...) has no capability check, and SMC-D negotiation needs no admin step on s390 or on x86 with the loopback ISM device loaded. Log an empty device name for SMC-D instead of dereferencing NULL.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-52941</guid>
    </item>
  </channel>
</rss>
