<?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 13:04:12 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-13715</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-13715</link>
      <description>bdu:2025-13715</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-13715</guid>
    </item>
    <item>
      <title>EUVD-2026-309600</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309600</link>
      <description>EUVD-2026-309600</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309600</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47221</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47221</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/slub: actually fix freelist pointer vs redzoning&lt;/p&gt;
&lt;p&gt;It turns out that SLUB redzoning (&amp;#34;slub_debug=Z&amp;#34;) checks from
s-&amp;gt;object_size rather than from s-&amp;gt;inuse (which is normally bumped to
make room for the freelist pointer), so a cache created with an object
size less than 24 would have the freelist pointer written beyond
s-&amp;gt;object_size, causing the redzone to be corrupted by the freelist
pointer.  This was very visible with &amp;#34;slub_debug=ZF&amp;#34;:&lt;/p&gt;
&lt;p&gt;BUG test (Tainted: G    B            ): Right Redzone overwritten
  -----------------------------------------------------------------------------&lt;/p&gt;
&lt;p&gt;INFO: 0xffff957ead1c05de-0xffff957ead1c05df @offset=1502. First byte 0x1a instead of 0xbb
  INFO: Slab 0xffffef3950b47000 objects=170 used=170 fp=0x0000000000000000 flags=0x8000000000000200
  INFO: Object 0xffff957ead1c05d8 @offset=1496 fp=0xffff957ead1c0620&lt;/p&gt;
&lt;p&gt;Redzone  (____ptrval____): bb bb bb bb bb bb bb bb               ........
  Object   (____ptrval____): 00 00 00 00 00 f6 f4 a5               ........
  Redzone  (____ptrval____): 40 1d e8 1a aa                        @....
  Padding  (____ptrval____): 00 00 00 00 00 00 00 00               ........&lt;/p&gt;
&lt;p&gt;Adjust the offset to stay within s-&amp;gt;object_size.&lt;/p&gt;
&lt;p&gt;(Note that no caches of in this size range are known to exist in the
kernel currently.)&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;mm/slub: actually fix freelist pointer vs redzoning&lt;/p&gt;
&lt;p&gt;It turns out that SLUB redzoning (&amp;#34;slub_debug=Z&amp;#34;) checks from
s-&amp;gt;object_size rather than from s-&amp;gt;inuse (which is normally bumped to
make room for the freelist pointer), so a cache created with an object
size less than 24 would have the freelist pointer written beyond
s-&amp;gt;object_size, causing the redzone to be corrupted by the freelist
pointer.  This was very visible with &amp;#34;slub_debug=ZF&amp;#34;:&lt;/p&gt;
&lt;p&gt;BUG test (Tainted: G    B            ): Right Redzone overwritten
  -----------------------------------------------------------------------------&lt;/p&gt;
&lt;p&gt;INFO: 0xffff957ead1c05de-0xffff957ead1c05df @offset=1502. First byte 0x1a instead of 0xbb
  INFO: Slab 0xffffef3950b47000 objects=170 used=170 fp=0x0000000000000000 flags=0x8000000000000200
  INFO: Object 0xffff957ead1c05d8 @offset=1496 fp=0xffff957ead1c0620&lt;/p&gt;
&lt;p&gt;Redzone  (____ptrval____): bb bb bb bb bb bb bb bb               ........
  Object   (____ptrval____): 00 00 00 00 00 f6 f4 a5               ........
  Redzone  (____ptrval____): 40 1d e8 1a aa                        @....
  Padding  (____ptrval____): 00 00 00 00 00 00 00 00               ........&lt;/p&gt;
&lt;p&gt;Adjust the offset to stay within s-&amp;gt;object_size.&lt;/p&gt;
&lt;p&gt;(Note that no caches of in this size range are known to exist in the
kernel currently.)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47221</guid>
    </item>
    <item>
      <title>GHSA-3c4w-p6cr-wgq6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3c4w-p6cr-wgq6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/slub: actually fix freelist pointer vs redzoning&lt;/p&gt;
&lt;p&gt;It turns out that SLUB redzoning (&amp;#34;slub_debug=Z&amp;#34;) checks from
s-&amp;gt;object_size rather than from s-&amp;gt;inuse (which is normally bumped to
make room for the freelist pointer), so a cache created with an object
size less than 24 would have the freelist pointer written beyond
s-&amp;gt;object_size, causing the redzone to be corrupted by the freelist
pointer.  This was very visible with &amp;#34;slub_debug=ZF&amp;#34;:&lt;/p&gt;
&lt;p&gt;BUG test (Tainted: G    B            ): Right Redzone overwritten
  -----------------------------------------------------------------------------&lt;/p&gt;
&lt;p&gt;INFO: 0xffff957ead1c05de-0xffff957ead1c05df @offset=1502. First byte 0x1a instead of 0xbb
  INFO: Slab 0xffffef3950b47000 objects=170 used=170 fp=0x0000000000000000 flags=0x8000000000000200
  INFO: Object 0xffff957ead1c05d8 @offset=1496 fp=0xffff957ead1c0620&lt;/p&gt;
&lt;p&gt;Redzone  (____ptrval____): bb bb bb bb bb bb bb bb               ........
  Object   (____ptrval____): 00 00 00 00 00 f6 f4 a5               ........
  Redzone  (____ptrval____): 40 1d e8 1a aa                        @....
  Padding  (____ptrval____): 00 00 00 00 00 00 00 00               ........&lt;/p&gt;
&lt;p&gt;Adjust the offset to stay within s-&amp;gt;object_size.&lt;/p&gt;
&lt;p&gt;(Note that no caches of in this size range are known to exist in the
kernel currently.)&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;mm/slub: actually fix freelist pointer vs redzoning&lt;/p&gt;
&lt;p&gt;It turns out that SLUB redzoning (&amp;#34;slub_debug=Z&amp;#34;) checks from
s-&amp;gt;object_size rather than from s-&amp;gt;inuse (which is normally bumped to
make room for the freelist pointer), so a cache created with an object
size less than 24 would have the freelist pointer written beyond
s-&amp;gt;object_size, causing the redzone to be corrupted by the freelist
pointer.  This was very visible with &amp;#34;slub_debug=ZF&amp;#34;:&lt;/p&gt;
&lt;p&gt;BUG test (Tainted: G    B            ): Right Redzone overwritten
  -----------------------------------------------------------------------------&lt;/p&gt;
&lt;p&gt;INFO: 0xffff957ead1c05de-0xffff957ead1c05df @offset=1502. First byte 0x1a instead of 0xbb
  INFO: Slab 0xffffef3950b47000 objects=170 used=170 fp=0x0000000000000000 flags=0x8000000000000200
  INFO: Object 0xffff957ead1c05d8 @offset=1496 fp=0xffff957ead1c0620&lt;/p&gt;
&lt;p&gt;Redzone  (____ptrval____): bb bb bb bb bb bb bb bb               ........
  Object   (____ptrval____): 00 00 00 00 00 f6 f4 a5               ........
  Redzone  (____ptrval____): 40 1d e8 1a aa                        @....
  Padding  (____ptrval____): 00 00 00 00 00 00 00 00               ........&lt;/p&gt;
&lt;p&gt;Adjust the offset to stay within s-&amp;gt;object_size.&lt;/p&gt;
&lt;p&gt;(Note that no caches of in this size range are known to exist in the
kernel currently.)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3c4w-p6cr-wgq6</guid>
    </item>
    <item>
      <title>gsd-2021-47221</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-47221</link>
      <description>gsd-2021-47221</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-47221</guid>
    </item>
    <item>
      <title>RHSA-2023:2951 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2023:2951</link>
      <description>&lt;p&gt;hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: when setting font with malicious data by ioctl PIO_FONT, kernel will write memory out of bounds kernel: mm/slub: actually fix freelist pointer vs redzoning kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: possible race condition in drivers/tty/tty_buffers.c kernel: use-after-free in ath9k_htc_probe_device() could cause an escalation of privileges kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: media: em28xx: initialize refcount before kref_get kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: use-after-free caused by l2cap_reassemble_sdu() in net/bluetooth/l2cap_core.c kernel: data races around icsk-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink reload in devlink_param_get kernel: USB-accessible buffer overflow in brcmfmac kernel: Double-free in split_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: when setting font with malicious data by ioctl PIO_FONT, kernel will write memory out of bounds kernel: mm/slub: actually fix freelist pointer vs redzoning kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: possible race condition in drivers/tty/tty_buffers.c kernel: use-after-free in ath9k_htc_probe_device() could cause an escalation of privileges kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: media: em28xx: initialize refcount before kref_get kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: use-after-free caused by l2cap_reassemble_sdu() in net/bluetooth/l2cap_core.c kernel: data races around icsk-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink reload in devlink_param_get kernel: USB-accessible buffer overflow in brcmfmac kernel: Double-free in split_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2023:2951</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47221</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47221</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 112 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/slub: actually fix freelist pointer vs redzoning It turns out that SLUB redzoning (&amp;#34;slub_debug=Z&amp;#34;) checks from s-&amp;gt;object_size rather than from s-&amp;gt;inuse (which is normally bumped to make room for the freelist pointer), so a cache created with an object size less than 24 would have the freelist pointer written beyond s-&amp;gt;object_size, causing the redzone to be corrupted by the freelist pointer.  This was very visible with &amp;#34;slub_debug=ZF&amp;#34;:   BUG test (Tainted: G    B            ): Right Redzone overwritten -----------------------------------------------------------------------------   INFO: 0xffff957ead1c05de-0xffff957ead1c05df @offset=1502. First byte 0x1a instead of 0xbb   INFO: Slab 0xffffef3950b47000 objects=170 used=170 fp=0x0000000000000000 flags=0x8000000000000200   INFO: Object 0xffff957ead1c05d8 @offset=1496 fp=0xffff957ead1c0620   Redzone  (____ptrval____): bb bb bb bb bb bb bb bb               ........   Object   (____ptrval____): 00 00 00 00 00 f6 f4 a5               ........   Redzone  (____ptrval____): 40 1d e8 1a aa                        @....   Padding  (____ptrval____): 00 00 00 00 00 00 00 00               ........ Adjust the offset to stay within s-&amp;gt;object_size. (Note that no caches of in this size range are known to exist in the kernel currently.)&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 112 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/slub: actually fix freelist pointer vs redzoning It turns out that SLUB redzoning (&amp;#34;slub_debug=Z&amp;#34;) checks from s-&amp;gt;object_size rather than from s-&amp;gt;inuse (which is normally bumped to make room for the freelist pointer), so a cache created with an object size less than 24 would have the freelist pointer written beyond s-&amp;gt;object_size, causing the redzone to be corrupted by the freelist pointer.  This was very visible with &amp;#34;slub_debug=ZF&amp;#34;:   BUG test (Tainted: G    B            ): Right Redzone overwritten -----------------------------------------------------------------------------   INFO: 0xffff957ead1c05de-0xffff957ead1c05df @offset=1502. First byte 0x1a instead of 0xbb   INFO: Slab 0xffffef3950b47000 objects=170 used=170 fp=0x0000000000000000 flags=0x8000000000000200   INFO: Object 0xffff957ead1c05d8 @offset=1496 fp=0xffff957ead1c0620   Redzone  (____ptrval____): bb bb bb bb bb bb bb bb               ........   Object   (____ptrval____): 00 00 00 00 00 f6 f4 a5               ........   Redzone  (____ptrval____): 40 1d e8 1a aa                        @....   Padding  (____ptrval____): 00 00 00 00 00 00 00 00               ........ Adjust the offset to stay within s-&amp;gt;object_size. (Note that no caches of in this size range are known to exist in the kernel currently.)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47221</guid>
    </item>
  </channel>
</rss>
