<?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 06:09:43 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72251</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-72251</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-72251</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1164 — 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-1164</link>
      <description>certfr-2026-avi-1164</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1164</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72251</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-72251</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_nat_sip: reload possible stale data pointer quoting sashiko:  ------------------------------------------------------------------------  [..] noticed a potential memory bug and header corruption involving the  SIP NAT helper.  In net/netfilter/nf_nat_sip.c:nf_nat_sip(): 	if (skb_ensure_writable(skb, skb-&amp;gt;len)) { 		nf_ct_helper_log(skb, ct, &amp;#34;cannot mangle packet&amp;#34;); 		return NF_DROP; 	} 	uh = (void *)skb-&amp;gt;data + protoff; 	uh-&amp;gt;dest = ct_sip_info-&amp;gt;forced_dport; 	if (!nf_nat_mangle_udp_packet(skb, ct, ctinfo, protoff, 				      0, 0, NULL, 0)) {  If a cloned or fragmented SKB is reallocated by skb_ensure_writable(), the  old data buffer is freed. However, nf_nat_sip() fails to update *dptr to  point to the new buffer.  It also appears to use nf_nat_mangle_udp_packet() on what could be a TCP  packet, which would overwrite the sequence number with a checksum update.  ------------------------------------------------------------------------ nf_conntrack_sip linerizes skbs, hence no fragmented skb can be seen. But clones are possible, so rebuild dptr. Disable nf_nat_mangle_udp_packet() branch for TCP streams. It doesn&amp;#39;t look like this can ever happen, else we should have received bug reports about this, so just check the conntrack is UDP and drop otherwise. The calling conntrack_sip set -&amp;gt;forced_dport for SIP_HDR_VIA_UDP messages, so I don&amp;#39;t think this is ever expected to be true for a TCP stream.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_nat_sip: reload possible stale data pointer quoting sashiko:  ------------------------------------------------------------------------  [..] noticed a potential memory bug and header corruption involving the  SIP NAT helper.  In net/netfilter/nf_nat_sip.c:nf_nat_sip(): 	if (skb_ensure_writable(skb, skb-&amp;gt;len)) { 		nf_ct_helper_log(skb, ct, &amp;#34;cannot mangle packet&amp;#34;); 		return NF_DROP; 	} 	uh = (void *)skb-&amp;gt;data + protoff; 	uh-&amp;gt;dest = ct_sip_info-&amp;gt;forced_dport; 	if (!nf_nat_mangle_udp_packet(skb, ct, ctinfo, protoff, 				      0, 0, NULL, 0)) {  If a cloned or fragmented SKB is reallocated by skb_ensure_writable(), the  old data buffer is freed. However, nf_nat_sip() fails to update *dptr to  point to the new buffer.  It also appears to use nf_nat_mangle_udp_packet() on what could be a TCP  packet, which would overwrite the sequence number with a checksum update.  ------------------------------------------------------------------------ nf_conntrack_sip linerizes skbs, hence no fragmented skb can be seen. But clones are possible, so rebuild dptr. Disable nf_nat_mangle_udp_packet() branch for TCP streams. It doesn&amp;#39;t look like this can ever happen, else we should have received bug reports about this, so just check the conntrack is UDP and drop otherwise. The calling conntrack_sip set -&amp;gt;forced_dport for SIP_HDR_VIA_UDP messages, so I don&amp;#39;t think this is ever expected to be true for a TCP stream.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-72251</guid>
    </item>
  </channel>
</rss>
