<?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 00:22:18 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03811</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03811</link>
      <description>bdu:2026-03811</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03811</guid>
    </item>
    <item>
      <title>EUVD-2026-344678</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344678</link>
      <description>EUVD-2026-344678</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344678</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49142</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49142</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: preserve skb_end_offset() in skb_unclone_keeptruesize()&lt;/p&gt;
&lt;p&gt;syzbot found another way to trigger the infamous WARN_ON_ONCE(delta &amp;lt; len)
in skb_try_coalesce() [1]&lt;/p&gt;
&lt;p&gt;I was able to root cause the issue to kfence.&lt;/p&gt;
&lt;p&gt;When kfence is in action, the following assertion is no longer true:&lt;/p&gt;
&lt;p&gt;int size = xxxx;
void *ptr1 = kmalloc(size, gfp);
void *ptr2 = kmalloc(size, gfp);&lt;/p&gt;
&lt;p&gt;if (ptr1 &amp;amp;&amp;amp; ptr2)
	ASSERT(ksize(ptr1) == ksize(ptr2));&lt;/p&gt;
&lt;p&gt;We attempted to fix these issues in the blamed commits, but forgot
that TCP was possibly shifting data after skb_unclone_keeptruesize()
has been used, notably from tcp_retrans_try_collapse().&lt;/p&gt;
&lt;p&gt;So we not only need to keep same skb-&amp;gt;truesize value,
we also need to make sure TCP wont fill new tailroom
that pskb_expand_head() was able to get from a
addr = kmalloc(...) followed by ksize(addr)&lt;/p&gt;
&lt;p&gt;Split skb_unclone_keeptruesize() into two parts:&lt;/p&gt;
&lt;p&gt;1) Inline skb_unclone_keeptruesize() for the common case,
   when skb is not cloned.&lt;/p&gt;
&lt;p&gt;2) Out of line __skb_unclone_keeptruesize() for the &amp;#39;slow path&amp;#39;.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 1 PID: 6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295
Modules linked in:
CPU: 1 PID: 6490 Comm: syz-executor161 Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295
Code: bf 01 00 00 00 0f b7 c0 89 c6 89 44…&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;net: preserve skb_end_offset() in skb_unclone_keeptruesize()&lt;/p&gt;
&lt;p&gt;syzbot found another way to trigger the infamous WARN_ON_ONCE(delta &amp;lt; len)
in skb_try_coalesce() [1]&lt;/p&gt;
&lt;p&gt;I was able to root cause the issue to kfence.&lt;/p&gt;
&lt;p&gt;When kfence is in action, the following assertion is no longer true:&lt;/p&gt;
&lt;p&gt;int size = xxxx;
void *ptr1 = kmalloc(size, gfp);
void *ptr2 = kmalloc(size, gfp);&lt;/p&gt;
&lt;p&gt;if (ptr1 &amp;amp;&amp;amp; ptr2)
	ASSERT(ksize(ptr1) == ksize(ptr2));&lt;/p&gt;
&lt;p&gt;We attempted to fix these issues in the blamed commits, but forgot
that TCP was possibly shifting data after skb_unclone_keeptruesize()
has been used, notably from tcp_retrans_try_collapse().&lt;/p&gt;
&lt;p&gt;So we not only need to keep same skb-&amp;gt;truesize value,
we also need to make sure TCP wont fill new tailroom
that pskb_expand_head() was able to get from a
addr = kmalloc(...) followed by ksize(addr)&lt;/p&gt;
&lt;p&gt;Split skb_unclone_keeptruesize() into two parts:&lt;/p&gt;
&lt;p&gt;1) Inline skb_unclone_keeptruesize() for the common case,
   when skb is not cloned.&lt;/p&gt;
&lt;p&gt;2) Out of line __skb_unclone_keeptruesize() for the &amp;#39;slow path&amp;#39;.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 1 PID: 6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295
Modules linked in:
CPU: 1 PID: 6490 Comm: syz-executor161 Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295
Code: bf 01 00 00 00 0f b7 c0 89 c6 89 44…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49142</guid>
    </item>
    <item>
      <title>GHSA-62rq-h65m-5cww</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-62rq-h65m-5cww</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: preserve skb_end_offset() in skb_unclone_keeptruesize()&lt;/p&gt;
&lt;p&gt;syzbot found another way to trigger the infamous WARN_ON_ONCE(delta &amp;lt; len)
in skb_try_coalesce() [1]&lt;/p&gt;
&lt;p&gt;I was able to root cause the issue to kfence.&lt;/p&gt;
&lt;p&gt;When kfence is in action, the following assertion is no longer true:&lt;/p&gt;
&lt;p&gt;int size = xxxx;
void *ptr1 = kmalloc(size, gfp);
void *ptr2 = kmalloc(size, gfp);&lt;/p&gt;
&lt;p&gt;if (ptr1 &amp;amp;&amp;amp; ptr2)
	ASSERT(ksize(ptr1) == ksize(ptr2));&lt;/p&gt;
&lt;p&gt;We attempted to fix these issues in the blamed commits, but forgot
that TCP was possibly shifting data after skb_unclone_keeptruesize()
has been used, notably from tcp_retrans_try_collapse().&lt;/p&gt;
&lt;p&gt;So we not only need to keep same skb-&amp;gt;truesize value,
we also need to make sure TCP wont fill new tailroom
that pskb_expand_head() was able to get from a
addr = kmalloc(...) followed by ksize(addr)&lt;/p&gt;
&lt;p&gt;Split skb_unclone_keeptruesize() into two parts:&lt;/p&gt;
&lt;p&gt;1) Inline skb_unclone_keeptruesize() for the common case,
   when skb is not cloned.&lt;/p&gt;
&lt;p&gt;2) Out of line __skb_unclone_keeptruesize() for the &amp;#39;slow path&amp;#39;.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 1 PID: 6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295
Modules linked in:
CPU: 1 PID: 6490 Comm: syz-executor161 Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295
Code: bf 01 00 00 00 0f b7 c0 89 c6 89 44…&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;net: preserve skb_end_offset() in skb_unclone_keeptruesize()&lt;/p&gt;
&lt;p&gt;syzbot found another way to trigger the infamous WARN_ON_ONCE(delta &amp;lt; len)
in skb_try_coalesce() [1]&lt;/p&gt;
&lt;p&gt;I was able to root cause the issue to kfence.&lt;/p&gt;
&lt;p&gt;When kfence is in action, the following assertion is no longer true:&lt;/p&gt;
&lt;p&gt;int size = xxxx;
void *ptr1 = kmalloc(size, gfp);
void *ptr2 = kmalloc(size, gfp);&lt;/p&gt;
&lt;p&gt;if (ptr1 &amp;amp;&amp;amp; ptr2)
	ASSERT(ksize(ptr1) == ksize(ptr2));&lt;/p&gt;
&lt;p&gt;We attempted to fix these issues in the blamed commits, but forgot
that TCP was possibly shifting data after skb_unclone_keeptruesize()
has been used, notably from tcp_retrans_try_collapse().&lt;/p&gt;
&lt;p&gt;So we not only need to keep same skb-&amp;gt;truesize value,
we also need to make sure TCP wont fill new tailroom
that pskb_expand_head() was able to get from a
addr = kmalloc(...) followed by ksize(addr)&lt;/p&gt;
&lt;p&gt;Split skb_unclone_keeptruesize() into two parts:&lt;/p&gt;
&lt;p&gt;1) Inline skb_unclone_keeptruesize() for the common case,
   when skb is not cloned.&lt;/p&gt;
&lt;p&gt;2) Out of line __skb_unclone_keeptruesize() for the &amp;#39;slow path&amp;#39;.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 1 PID: 6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295
Modules linked in:
CPU: 1 PID: 6490 Comm: syz-executor161 Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295
Code: bf 01 00 00 00 0f b7 c0 89 c6 89 44…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-62rq-h65m-5cww</guid>
    </item>
    <item>
      <title>RHSA-2022:8267 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2022:8267</link>
      <description>&lt;p&gt;kernel: off-path attacker may inject data or terminate victim&amp;#39;s TCP session kernel: use-after-free vulnerability in function sco_sock_sendmsg() kernel: fix &amp;#39;struct pid&amp;#39; leaks in &amp;#39;dbgfs_target_ids_write()&amp;#39; kernel: veth: ensure skb entering GRO are not cloned. kernel: inet: fully convert sk-&amp;gt;sk_rx_dst to RCU rules kernel: irqchip/gic-v3-its: Fix potential VPE leak on error kernel: nvme-rdma: destroy cm id before destroy qp to avoid use after free kernel: ptp: Fix possible memory leak in ptp_clock_register() kernel: ethtool: do not perform operations on net devices being unregistered kernel: ethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce() kernel: net: nexthop: fix null pointer dereference when IPv6 is not enabled kernel: scsi: scsi_debug: Fix type in min_t to avoid stack OOB kernel: KVM: x86/mmu: Zap _all_ roots when unmapping gfn range in TDP MMU kernel: Revert &amp;#34;Revert &amp;#34;block, bfq: honor already-setup queue merges&amp;#34;&amp;#34; kernel: udmabuf: validate ubuf-&amp;gt;pagecount kernel: drm/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free() kernel: smb2_ioctl_query_info NULL pointer dereference kernel: NULL pointer dereference in udf_expand_file_adinicbdue() during writeback kernel: swiotlb information leak with DMA_FROM_DEVICE kernel: uninitialized registers on stack in nft_do_chain can cause kernel pointer leakage to UM kernel: race condition in snd_pcm_hw_free leading to use-after-free kernel: KVM: cmpxchg_gpte can write to pfns outside the userspace region ke…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: off-path attacker may inject data or terminate victim&amp;#39;s TCP session kernel: use-after-free vulnerability in function sco_sock_sendmsg() kernel: fix &amp;#39;struct pid&amp;#39; leaks in &amp;#39;dbgfs_target_ids_write()&amp;#39; kernel: veth: ensure skb entering GRO are not cloned. kernel: inet: fully convert sk-&amp;gt;sk_rx_dst to RCU rules kernel: irqchip/gic-v3-its: Fix potential VPE leak on error kernel: nvme-rdma: destroy cm id before destroy qp to avoid use after free kernel: ptp: Fix possible memory leak in ptp_clock_register() kernel: ethtool: do not perform operations on net devices being unregistered kernel: ethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce() kernel: net: nexthop: fix null pointer dereference when IPv6 is not enabled kernel: scsi: scsi_debug: Fix type in min_t to avoid stack OOB kernel: KVM: x86/mmu: Zap _all_ roots when unmapping gfn range in TDP MMU kernel: Revert &amp;#34;Revert &amp;#34;block, bfq: honor already-setup queue merges&amp;#34;&amp;#34; kernel: udmabuf: validate ubuf-&amp;gt;pagecount kernel: drm/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free() kernel: smb2_ioctl_query_info NULL pointer dereference kernel: NULL pointer dereference in udf_expand_file_adinicbdue() during writeback kernel: swiotlb information leak with DMA_FROM_DEVICE kernel: uninitialized registers on stack in nft_do_chain can cause kernel pointer leakage to UM kernel: race condition in snd_pcm_hw_free leading to use-after-free kernel: KVM: cmpxchg_gpte can write to pfns outside the userspace region ke…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2022:8267</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49142</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49142</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: preserve skb_end_offset() in skb_unclone_keeptruesize() syzbot found another way to trigger the infamous WARN_ON_ONCE(delta &amp;lt; len) in skb_try_coalesce() [1] I was able to root cause the issue to kfence. When kfence is in action, the following assertion is no longer true: int size = xxxx; void *ptr1 = kmalloc(size, gfp); void *ptr2 = kmalloc(size, gfp); if (ptr1 &amp;amp;&amp;amp; ptr2) 	ASSERT(ksize(ptr1) == ksize(ptr2)); We attempted to fix these issues in the blamed commits, but forgot that TCP was possibly shifting data after skb_unclone_keeptruesize() has been used, notably from tcp_retrans_try_collapse(). So we not only need to keep same skb-&amp;gt;truesize value, we also need to make sure TCP wont fill new tailroom that pskb_expand_head() was able to get from a addr = kmalloc(...) followed by ksize(addr) Split skb_unclone_keeptruesize() into two parts: 1) Inline skb_unclone_keeptruesize() for the common case,    when skb is not cloned. 2) Out of line __skb_unclone_keeptruesize() for the &amp;#39;slow path&amp;#39;. WARNING: CPU: 1 PID: 6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 Modules linked in: CPU: 1 PID: 6490 Comm: syz-executor161 Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 Code: bf 01 00 00 00 0f b7 c0 89 c6 89 44 24 20 e8 62…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: preserve skb_end_offset() in skb_unclone_keeptruesize() syzbot found another way to trigger the infamous WARN_ON_ONCE(delta &amp;lt; len) in skb_try_coalesce() [1] I was able to root cause the issue to kfence. When kfence is in action, the following assertion is no longer true: int size = xxxx; void *ptr1 = kmalloc(size, gfp); void *ptr2 = kmalloc(size, gfp); if (ptr1 &amp;amp;&amp;amp; ptr2) 	ASSERT(ksize(ptr1) == ksize(ptr2)); We attempted to fix these issues in the blamed commits, but forgot that TCP was possibly shifting data after skb_unclone_keeptruesize() has been used, notably from tcp_retrans_try_collapse(). So we not only need to keep same skb-&amp;gt;truesize value, we also need to make sure TCP wont fill new tailroom that pskb_expand_head() was able to get from a addr = kmalloc(...) followed by ksize(addr) Split skb_unclone_keeptruesize() into two parts: 1) Inline skb_unclone_keeptruesize() for the common case,    when skb is not cloned. 2) Out of line __skb_unclone_keeptruesize() for the &amp;#39;slow path&amp;#39;. WARNING: CPU: 1 PID: 6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 Modules linked in: CPU: 1 PID: 6490 Comm: syz-executor161 Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 Code: bf 01 00 00 00 0f b7 c0 89 c6 89 44 24 20 e8 62…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49142</guid>
    </item>
  </channel>
</rss>
