<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 12:13:08 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-14270</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-14270</link>
      <description>bdu:2026-14270</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-14270</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-64132</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-64132</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://vulnerability.circl.lu/vuln/bell-cve-2026-64132</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — 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://vulnerability.circl.lu/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64132</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-64132</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: ioam: refresh hdr pointer before ioam6_event()&lt;/p&gt;
&lt;p&gt;Reported by Sashiko:&lt;/p&gt;
&lt;p&gt;In ipv6_hop_ioam(), the hdr pointer is initialized to point into the
skb&amp;#39;s linear data buffer. Later, the code calls skb_ensure_writable(),
which might reallocate the buffer:&lt;/p&gt;
&lt;p&gt;if (skb_ensure_writable(skb, optoff + 2 + hdr-&amp;gt;opt_len))
		goto drop;&lt;/p&gt;
&lt;p&gt;/* Trace pointer may have changed */
	trace = (struct ioam6_trace_hdr *)(skb_network_header(skb)
					   + optoff + sizeof(*hdr));&lt;/p&gt;
&lt;p&gt;ioam6_fill_trace_data(skb, ns, trace, true);&lt;/p&gt;
&lt;p&gt;ioam6_event(IOAM6_EVENT_TRACE, dev_net(skb-&amp;gt;dev),
		    GFP_ATOMIC, (void *)trace, hdr-&amp;gt;opt_len - 2);&lt;/p&gt;
&lt;p&gt;If the skb is cloned or lacks sufficient linear headroom,
skb_ensure_writable() will invoke pskb_expand_head(), which reallocates
the skb&amp;#39;s data buffer and frees the old one, invalidating pointers to
it. While the code recalculates the trace pointer immediately after the
call to skb_ensure_writable(), it fails to recalculate the hdr pointer.&lt;/p&gt;
&lt;p&gt;This patch fixes the above by recalculating the hdr pointer before
passing hdr-&amp;gt;opt_len to ioam6_event(), so that we avoid any UaF.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: ioam: refresh hdr pointer before ioam6_event()&lt;/p&gt;
&lt;p&gt;Reported by Sashiko:&lt;/p&gt;
&lt;p&gt;In ipv6_hop_ioam(), the hdr pointer is initialized to point into the
skb&amp;#39;s linear data buffer. Later, the code calls skb_ensure_writable(),
which might reallocate the buffer:&lt;/p&gt;
&lt;p&gt;if (skb_ensure_writable(skb, optoff + 2 + hdr-&amp;gt;opt_len))
		goto drop;&lt;/p&gt;
&lt;p&gt;/* Trace pointer may have changed */
	trace = (struct ioam6_trace_hdr *)(skb_network_header(skb)
					   + optoff + sizeof(*hdr));&lt;/p&gt;
&lt;p&gt;ioam6_fill_trace_data(skb, ns, trace, true);&lt;/p&gt;
&lt;p&gt;ioam6_event(IOAM6_EVENT_TRACE, dev_net(skb-&amp;gt;dev),
		    GFP_ATOMIC, (void *)trace, hdr-&amp;gt;opt_len - 2);&lt;/p&gt;
&lt;p&gt;If the skb is cloned or lacks sufficient linear headroom,
skb_ensure_writable() will invoke pskb_expand_head(), which reallocates
the skb&amp;#39;s data buffer and frees the old one, invalidating pointers to
it. While the code recalculates the trace pointer immediately after the
call to skb_ensure_writable(), it fails to recalculate the hdr pointer.&lt;/p&gt;
&lt;p&gt;This patch fixes the above by recalculating the hdr pointer before
passing hdr-&amp;gt;opt_len to ioam6_event(), so that we avoid any UaF.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-64132</guid>
    </item>
    <item>
      <title>GHSA-ph8w-wrch-h8v5</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-ph8w-wrch-h8v5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: ioam: refresh hdr pointer before ioam6_event()&lt;/p&gt;
&lt;p&gt;Reported by Sashiko:&lt;/p&gt;
&lt;p&gt;In ipv6_hop_ioam(), the hdr pointer is initialized to point into the
skb&amp;#39;s linear data buffer. Later, the code calls skb_ensure_writable(),
which might reallocate the buffer:&lt;/p&gt;
&lt;p&gt;if (skb_ensure_writable(skb, optoff + 2 + hdr-&amp;gt;opt_len))
		goto drop;&lt;/p&gt;
&lt;p&gt;/* Trace pointer may have changed */
	trace = (struct ioam6_trace_hdr *)(skb_network_header(skb)
					   + optoff + sizeof(*hdr));&lt;/p&gt;
&lt;p&gt;ioam6_fill_trace_data(skb, ns, trace, true);&lt;/p&gt;
&lt;p&gt;ioam6_event(IOAM6_EVENT_TRACE, dev_net(skb-&amp;gt;dev),
		    GFP_ATOMIC, (void *)trace, hdr-&amp;gt;opt_len - 2);&lt;/p&gt;
&lt;p&gt;If the skb is cloned or lacks sufficient linear headroom,
skb_ensure_writable() will invoke pskb_expand_head(), which reallocates
the skb&amp;#39;s data buffer and frees the old one, invalidating pointers to
it. While the code recalculates the trace pointer immediately after the
call to skb_ensure_writable(), it fails to recalculate the hdr pointer.&lt;/p&gt;
&lt;p&gt;This patch fixes the above by recalculating the hdr pointer before
passing hdr-&amp;gt;opt_len to ioam6_event(), so that we avoid any UaF.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: ioam: refresh hdr pointer before ioam6_event()&lt;/p&gt;
&lt;p&gt;Reported by Sashiko:&lt;/p&gt;
&lt;p&gt;In ipv6_hop_ioam(), the hdr pointer is initialized to point into the
skb&amp;#39;s linear data buffer. Later, the code calls skb_ensure_writable(),
which might reallocate the buffer:&lt;/p&gt;
&lt;p&gt;if (skb_ensure_writable(skb, optoff + 2 + hdr-&amp;gt;opt_len))
		goto drop;&lt;/p&gt;
&lt;p&gt;/* Trace pointer may have changed */
	trace = (struct ioam6_trace_hdr *)(skb_network_header(skb)
					   + optoff + sizeof(*hdr));&lt;/p&gt;
&lt;p&gt;ioam6_fill_trace_data(skb, ns, trace, true);&lt;/p&gt;
&lt;p&gt;ioam6_event(IOAM6_EVENT_TRACE, dev_net(skb-&amp;gt;dev),
		    GFP_ATOMIC, (void *)trace, hdr-&amp;gt;opt_len - 2);&lt;/p&gt;
&lt;p&gt;If the skb is cloned or lacks sufficient linear headroom,
skb_ensure_writable() will invoke pskb_expand_head(), which reallocates
the skb&amp;#39;s data buffer and frees the old one, invalidating pointers to
it. While the code recalculates the trace pointer immediately after the
call to skb_ensure_writable(), it fails to recalculate the hdr pointer.&lt;/p&gt;
&lt;p&gt;This patch fixes the above by recalculating the hdr pointer before
passing hdr-&amp;gt;opt_len to ioam6_event(), so that we avoid any UaF.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-ph8w-wrch-h8v5</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64132</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64132</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 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: refresh hdr pointer before ioam6_event() Reported by Sashiko: In ipv6_hop_ioam(), the hdr pointer is initialized to point into the skb&amp;#39;s linear data buffer. Later, the code calls skb_ensure_writable(), which might reallocate the buffer: 	if (skb_ensure_writable(skb, optoff + 2 + hdr-&amp;gt;opt_len)) 		goto drop; 	/* Trace pointer may have changed */ 	trace = (struct ioam6_trace_hdr *)(skb_network_header(skb) 					   + optoff + sizeof(*hdr)); 	ioam6_fill_trace_data(skb, ns, trace, true); 	ioam6_event(IOAM6_EVENT_TRACE, dev_net(skb-&amp;gt;dev), 		    GFP_ATOMIC, (void *)trace, hdr-&amp;gt;opt_len - 2); If the skb is cloned or lacks sufficient linear headroom, skb_ensure_writable() will invoke pskb_expand_head(), which reallocates the skb&amp;#39;s data buffer and frees the old one, invalidating pointers to it. While the code recalculates the trace pointer immediately after the call to skb_ensure_writable(), it fails to recalculate the hdr pointer. This patch fixes the above by recalculating the hdr pointer before passing hdr-&amp;gt;opt_len to ioam6_event(), so that we avoid any UaF.&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 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: refresh hdr pointer before ioam6_event() Reported by Sashiko: In ipv6_hop_ioam(), the hdr pointer is initialized to point into the skb&amp;#39;s linear data buffer. Later, the code calls skb_ensure_writable(), which might reallocate the buffer: 	if (skb_ensure_writable(skb, optoff + 2 + hdr-&amp;gt;opt_len)) 		goto drop; 	/* Trace pointer may have changed */ 	trace = (struct ioam6_trace_hdr *)(skb_network_header(skb) 					   + optoff + sizeof(*hdr)); 	ioam6_fill_trace_data(skb, ns, trace, true); 	ioam6_event(IOAM6_EVENT_TRACE, dev_net(skb-&amp;gt;dev), 		    GFP_ATOMIC, (void *)trace, hdr-&amp;gt;opt_len - 2); If the skb is cloned or lacks sufficient linear headroom, skb_ensure_writable() will invoke pskb_expand_head(), which reallocates the skb&amp;#39;s data buffer and frees the old one, invalidating pointers to it. While the code recalculates the trace pointer immediately after the call to skb_ensure_writable(), it fails to recalculate the hdr pointer. This patch fixes the above by recalculating the hdr pointer before passing hdr-&amp;gt;opt_len to ioam6_event(), so that we avoid any UaF.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64132</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2403</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
