<?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 07:38:45 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98801</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-98801</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-98801</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1375 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1375</link>
      <description>certfr-2026-avi-1375</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1375</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98801</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98801</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: net: restrict SO_RESERVE_MEM to TCP sockets and cap max value Commit 2bb2f5fb21b0 (&amp;#34;net: add new socket option SO_RESERVE_MEM&amp;#34;) and commit d00c8ee31729 (&amp;#34;net: fix possible NULL deref in sock_reserve_memory&amp;#34;) only checked sk_has_account(sk), which is true for both TCP and UDP sockets. However, SO_RESERVE_MEM and sk_unused_reserved_mem() are currently only supported by TCP: - On UDP sockets, sk-&amp;gt;sk_forward_alloc is protected by   sk-&amp;gt;sk_receive_queue.lock, whereas sock_reserve_memory() and   sock_release_reserved_memory() only acquire lock_sock(sk). Concurrent   UDP packet reception/release and setsockopt(SO_RESERVE_MEM) corrupt   sk_forward_alloc and memcg accounting. - udp_rmem_release() reclaims excess sk_forward_alloc without   accounting for sk_unused_reserved_mem(sk). Restrict sock_reserve_memory() to TCP sockets (sk_is_tcp(sk)) for now. Supporting SO_RESERVE_MEM for UDP (acquiring sk_receive_queue.lock and honoring sk_unused_reserved_mem() in udp_rmem_release()) can be done in a future net-next series if needed. In addition, reject val &amp;gt; SZ_1G with -EINVAL in sk_setsockopt(SO_RESERVE_MEM). Without an upper bound, values near INT_MAX cause sk_mem_pages(delta) and (pages &amp;lt;&amp;lt; PAGE_SHIFT) to overflow 32-bit signed int, corrupting sk-&amp;gt;sk_forward_alloc and sk-&amp;gt;sk_reserved_mem. Using a page-aligned cap (SZ_1G) ensures that the page-rounded sk-&amp;gt;sk_reserved_mem reported by getsockopt(SO_RESERVE_MEM) can always be…&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: net: restrict SO_RESERVE_MEM to TCP sockets and cap max value Commit 2bb2f5fb21b0 (&amp;#34;net: add new socket option SO_RESERVE_MEM&amp;#34;) and commit d00c8ee31729 (&amp;#34;net: fix possible NULL deref in sock_reserve_memory&amp;#34;) only checked sk_has_account(sk), which is true for both TCP and UDP sockets. However, SO_RESERVE_MEM and sk_unused_reserved_mem() are currently only supported by TCP: - On UDP sockets, sk-&amp;gt;sk_forward_alloc is protected by   sk-&amp;gt;sk_receive_queue.lock, whereas sock_reserve_memory() and   sock_release_reserved_memory() only acquire lock_sock(sk). Concurrent   UDP packet reception/release and setsockopt(SO_RESERVE_MEM) corrupt   sk_forward_alloc and memcg accounting. - udp_rmem_release() reclaims excess sk_forward_alloc without   accounting for sk_unused_reserved_mem(sk). Restrict sock_reserve_memory() to TCP sockets (sk_is_tcp(sk)) for now. Supporting SO_RESERVE_MEM for UDP (acquiring sk_receive_queue.lock and honoring sk_unused_reserved_mem() in udp_rmem_release()) can be done in a future net-next series if needed. In addition, reject val &amp;gt; SZ_1G with -EINVAL in sk_setsockopt(SO_RESERVE_MEM). Without an upper bound, values near INT_MAX cause sk_mem_pages(delta) and (pages &amp;lt;&amp;lt; PAGE_SHIFT) to overflow 32-bit signed int, corrupting sk-&amp;gt;sk_forward_alloc and sk-&amp;gt;sk_reserved_mem. Using a page-aligned cap (SZ_1G) ensures that the page-rounded sk-&amp;gt;sk_reserved_mem reported by getsockopt(SO_RESERVE_MEM) can always be…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98801</guid>
    </item>
  </channel>
</rss>
