<?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://cve.radiocsirt.org</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, 03 Oct 2026 07:13:44 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-09713</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-09713</link>
      <description>bdu:2026-09713</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-09713</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-53362</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-53362</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://cve.radiocsirt.org/vuln/bell-cve-2026-53362</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0855 — De multiples vulnérabilités ont été découvertes dans Microsoft Azure Linux. Elles permettent à un attaquant de provoque…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0855</link>
      <description>certfr-2026-avi-0855</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0855</guid>
    </item>
    <item>
      <title>EUVD-2026-361298</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361298</link>
      <description>EUVD-2026-361298</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361298</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53362</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53362</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: account for fraggap on the paged allocation path&lt;/p&gt;
&lt;p&gt;In __ip6_append_data(), when the paged-allocation branch is taken
(MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are
computed as&lt;/p&gt;
&lt;p&gt;alloclen = fragheaderlen + transhdrlen;
	pagedlen = datalen - transhdrlen;&lt;/p&gt;
&lt;p&gt;datalen already includes fraggap (datalen = length + fraggap). When
fraggap is non-zero, this is not the first skb and transhdrlen is zero.
The fraggap bytes carried over from the previous skb are copied just past
the fragment headers in the new skb&amp;#39;s linear area. The linear area is
therefore undersized by fraggap bytes while pagedlen is overstated by the
same amount, and the copy writes past skb-&amp;gt;end into the trailing
skb_shared_info.&lt;/p&gt;
&lt;p&gt;An unprivileged user can trigger this via a UDPv6 socket using
MSG_MORE together with MSG_SPLICE_PAGES.&lt;/p&gt;
&lt;p&gt;The bad accounting was introduced by commit 773ba4fe9104 (&amp;#34;ipv6:
avoid partial copy for zc&amp;#34;). Before commit ce650a166335 (&amp;#34;udp6: Fix
__ip6_append_data()&amp;#39;s handling of MSG_SPLICE_PAGES&amp;#34;), the negative
copy value caused -EINVAL to be returned. That later commit allowed
MSG_SPLICE_PAGES to proceed in this case, making the corruption
triggerable.&lt;/p&gt;
&lt;p&gt;The non-paged branch sets alloclen to fraglen, which already accounts
for fraggap because datalen does. Bring the paged branch in line by
adding fraggap to alloclen and subtracting it from pagedlen.&lt;/p&gt;
&lt;p&gt;After this adjustment, copy no longer collapses to -fraggap…&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: account for fraggap on the paged allocation path&lt;/p&gt;
&lt;p&gt;In __ip6_append_data(), when the paged-allocation branch is taken
(MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are
computed as&lt;/p&gt;
&lt;p&gt;alloclen = fragheaderlen + transhdrlen;
	pagedlen = datalen - transhdrlen;&lt;/p&gt;
&lt;p&gt;datalen already includes fraggap (datalen = length + fraggap). When
fraggap is non-zero, this is not the first skb and transhdrlen is zero.
The fraggap bytes carried over from the previous skb are copied just past
the fragment headers in the new skb&amp;#39;s linear area. The linear area is
therefore undersized by fraggap bytes while pagedlen is overstated by the
same amount, and the copy writes past skb-&amp;gt;end into the trailing
skb_shared_info.&lt;/p&gt;
&lt;p&gt;An unprivileged user can trigger this via a UDPv6 socket using
MSG_MORE together with MSG_SPLICE_PAGES.&lt;/p&gt;
&lt;p&gt;The bad accounting was introduced by commit 773ba4fe9104 (&amp;#34;ipv6:
avoid partial copy for zc&amp;#34;). Before commit ce650a166335 (&amp;#34;udp6: Fix
__ip6_append_data()&amp;#39;s handling of MSG_SPLICE_PAGES&amp;#34;), the negative
copy value caused -EINVAL to be returned. That later commit allowed
MSG_SPLICE_PAGES to proceed in this case, making the corruption
triggerable.&lt;/p&gt;
&lt;p&gt;The non-paged branch sets alloclen to fraglen, which already accounts
for fraggap because datalen does. Bring the paged branch in line by
adding fraggap to alloclen and subtracting it from pagedlen.&lt;/p&gt;
&lt;p&gt;After this adjustment, copy no longer collapses to -fraggap…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53362</guid>
    </item>
    <item>
      <title>GHSA-3x6f-vm7x-cgm7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3x6f-vm7x-cgm7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: account for fraggap on the paged allocation path&lt;/p&gt;
&lt;p&gt;In __ip6_append_data(), when the paged-allocation branch is taken
(MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are
computed as&lt;/p&gt;
&lt;p&gt;alloclen = fragheaderlen + transhdrlen;
	pagedlen = datalen - transhdrlen;&lt;/p&gt;
&lt;p&gt;datalen already includes fraggap (datalen = length + fraggap). When
fraggap is non-zero, this is not the first skb and transhdrlen is zero.
The fraggap bytes carried over from the previous skb are copied just past
the fragment headers in the new skb&amp;#39;s linear area. The linear area is
therefore undersized by fraggap bytes while pagedlen is overstated by the
same amount, and the copy writes past skb-&amp;gt;end into the trailing
skb_shared_info.&lt;/p&gt;
&lt;p&gt;An unprivileged user can trigger this via a UDPv6 socket using
MSG_MORE together with MSG_SPLICE_PAGES.&lt;/p&gt;
&lt;p&gt;The bad accounting was introduced by commit 773ba4fe9104 (&amp;#34;ipv6:
avoid partial copy for zc&amp;#34;). Before commit ce650a166335 (&amp;#34;udp6: Fix
__ip6_append_data()&amp;#39;s handling of MSG_SPLICE_PAGES&amp;#34;), the negative
copy value caused -EINVAL to be returned. That later commit allowed
MSG_SPLICE_PAGES to proceed in this case, making the corruption
triggerable.&lt;/p&gt;
&lt;p&gt;The non-paged branch sets alloclen to fraglen, which already accounts
for fraggap because datalen does. Bring the paged branch in line by
adding fraggap to alloclen and subtracting it from pagedlen.&lt;/p&gt;
&lt;p&gt;After this adjustment, copy no longer collapses to -fraggap…&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: account for fraggap on the paged allocation path&lt;/p&gt;
&lt;p&gt;In __ip6_append_data(), when the paged-allocation branch is taken
(MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are
computed as&lt;/p&gt;
&lt;p&gt;alloclen = fragheaderlen + transhdrlen;
	pagedlen = datalen - transhdrlen;&lt;/p&gt;
&lt;p&gt;datalen already includes fraggap (datalen = length + fraggap). When
fraggap is non-zero, this is not the first skb and transhdrlen is zero.
The fraggap bytes carried over from the previous skb are copied just past
the fragment headers in the new skb&amp;#39;s linear area. The linear area is
therefore undersized by fraggap bytes while pagedlen is overstated by the
same amount, and the copy writes past skb-&amp;gt;end into the trailing
skb_shared_info.&lt;/p&gt;
&lt;p&gt;An unprivileged user can trigger this via a UDPv6 socket using
MSG_MORE together with MSG_SPLICE_PAGES.&lt;/p&gt;
&lt;p&gt;The bad accounting was introduced by commit 773ba4fe9104 (&amp;#34;ipv6:
avoid partial copy for zc&amp;#34;). Before commit ce650a166335 (&amp;#34;udp6: Fix
__ip6_append_data()&amp;#39;s handling of MSG_SPLICE_PAGES&amp;#34;), the negative
copy value caused -EINVAL to be returned. That later commit allowed
MSG_SPLICE_PAGES to proceed in this case, making the corruption
triggerable.&lt;/p&gt;
&lt;p&gt;The non-paged branch sets alloclen to fraglen, which already accounts
for fraggap because datalen does. Bring the paged branch in line by
adding fraggap to alloclen and subtracting it from pagedlen.&lt;/p&gt;
&lt;p&gt;After this adjustment, copy no longer collapses to -fraggap…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3x6f-vm7x-cgm7</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-53362 — ipv6: account for fraggap on the paged allocation path</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-53362</link>
      <description>msrc_CVE-2026-53362</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-53362</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11214-1 — kernel-devel-7.1.3-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11214-1</link>
      <description>&lt;p&gt;kernel-devel-7.1.3-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.1.3-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11214-1</guid>
    </item>
    <item>
      <title>RHSA-2026:34927 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:34927</link>
      <description>&lt;p&gt;kernel: kernel: ipv6 frag escape&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: kernel: ipv6 frag escape&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:34927</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:22521-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:22521-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:22521-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53362</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53362</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: ipv6: account for fraggap on the paged allocation path In __ip6_append_data(), when the paged-allocation branch is taken (MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are computed as 	alloclen = fragheaderlen + transhdrlen; 	pagedlen = datalen - transhdrlen; datalen already includes fraggap (datalen = length + fraggap). When fraggap is non-zero, this is not the first skb and transhdrlen is zero. The fraggap bytes carried over from the previous skb are copied just past the fragment headers in the new skb&amp;#39;s linear area. The linear area is therefore undersized by fraggap bytes while pagedlen is overstated by the same amount, and the copy writes past skb-&amp;gt;end into the trailing skb_shared_info. An unprivileged user can trigger this via a UDPv6 socket using MSG_MORE together with MSG_SPLICE_PAGES. The bad accounting was introduced by commit 773ba4fe9104 (&amp;#34;ipv6: avoid partial copy for zc&amp;#34;). Before commit ce650a166335 (&amp;#34;udp6: Fix __ip6_append_data()&amp;#39;s handling of MSG_SPLICE_PAGES&amp;#34;), the negative copy value caused -EINVAL to be returned. That later commit allowed MSG_SPLICE_PAGES to proceed in this case, making the corruption triggerable. The non-paged branch sets alloclen to fraglen, which already accounts for fraggap because datalen does. Bring the paged branch in line by adding fraggap to alloclen and subtracting it from pagedlen. After this adjustment, copy no longer collapses to -fraggap on the…&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: ipv6: account for fraggap on the paged allocation path In __ip6_append_data(), when the paged-allocation branch is taken (MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are computed as 	alloclen = fragheaderlen + transhdrlen; 	pagedlen = datalen - transhdrlen; datalen already includes fraggap (datalen = length + fraggap). When fraggap is non-zero, this is not the first skb and transhdrlen is zero. The fraggap bytes carried over from the previous skb are copied just past the fragment headers in the new skb&amp;#39;s linear area. The linear area is therefore undersized by fraggap bytes while pagedlen is overstated by the same amount, and the copy writes past skb-&amp;gt;end into the trailing skb_shared_info. An unprivileged user can trigger this via a UDPv6 socket using MSG_MORE together with MSG_SPLICE_PAGES. The bad accounting was introduced by commit 773ba4fe9104 (&amp;#34;ipv6: avoid partial copy for zc&amp;#34;). Before commit ce650a166335 (&amp;#34;udp6: Fix __ip6_append_data()&amp;#39;s handling of MSG_SPLICE_PAGES&amp;#34;), the negative copy value caused -EINVAL to be returned. That later commit allowed MSG_SPLICE_PAGES to proceed in this case, making the corruption triggerable. The non-paged branch sets alloclen to fraglen, which already accounts for fraggap because datalen does. Bring the paged branch in line by adding fraggap to alloclen and subtracting it from pagedlen. After this adjustment, copy no longer collapses to -fraggap on the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53362</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2208 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2208</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Speicherbeschädigungen zu verursachen, Kernel-Speicher offenzulegen oder Denial-of-Service-Zustände auszulösen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Speicherbeschädigungen zu verursachen, Kernel-Speicher offenzulegen oder Denial-of-Service-Zustände auszulösen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2208</guid>
    </item>
  </channel>
</rss>
