<?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>Fri, 02 Oct 2026 22:54:02 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:71700 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2026:71700</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 64 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: fbcon: Set fb_display[i]-&amp;gt;mode to NULL when the mode is released (CVE-2025-40323)
  * kernel: smb: smbdirect: introduce smbdirect_socket.recv_io.credits.available (CVE-2026-31539)
  * kernel: drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (CVE-2026-46230)
  * kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (CVE-2026-46204)
  * kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (CVE-2026-46199)
  * kernel: drm/amdgpu/userq: fix access to stale wptr mapping (CVE-2026-46311)
  * kernel: netfilter: nf_queue: hold bridge skb-&amp;gt;dev while queued (CVE-2026-52912)
  * kernel: accel/ivpu: Add buffer overflow check in MS get_info_ioctl (CVE-2026-53203)
  * kernel: drm/xe/eustall: Fix drm_dev_put called before stream disable in close (CVE-2026-53290)
  * kernel: drm/virtio: use uninterruptible resv lock for plane updates (CVE-2026-64098)
  * kernel: Linux kernel: PPPoE memory corruption via stale pointer (CVE-2026-68121)
  * kernel: drm/amdgpu/vce: fix integer overflow in image size (CVE-2026-68108)
  * kernel: drm/amdkfd: fix 32-bit overflow in CWSR total size calculation (CVE-2026-68257)
  * kernel: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists (CVE-2026-68267)
  * kernel: drm/xe: Hold a dma-buf reference for imported BOs (CVE-2026-68266)
  * kernel: drm/amdgpu: Fix context pstate override handling (CVE-2026-68273)
  *…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 64 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: fbcon: Set fb_display[i]-&amp;gt;mode to NULL when the mode is released (CVE-2025-40323)
  * kernel: smb: smbdirect: introduce smbdirect_socket.recv_io.credits.available (CVE-2026-31539)
  * kernel: drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (CVE-2026-46230)
  * kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (CVE-2026-46204)
  * kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (CVE-2026-46199)
  * kernel: drm/amdgpu/userq: fix access to stale wptr mapping (CVE-2026-46311)
  * kernel: netfilter: nf_queue: hold bridge skb-&amp;gt;dev while queued (CVE-2026-52912)
  * kernel: accel/ivpu: Add buffer overflow check in MS get_info_ioctl (CVE-2026-53203)
  * kernel: drm/xe/eustall: Fix drm_dev_put called before stream disable in close (CVE-2026-53290)
  * kernel: drm/virtio: use uninterruptible resv lock for plane updates (CVE-2026-64098)
  * kernel: Linux kernel: PPPoE memory corruption via stale pointer (CVE-2026-68121)
  * kernel: drm/amdgpu/vce: fix integer overflow in image size (CVE-2026-68108)
  * kernel: drm/amdkfd: fix 32-bit overflow in CWSR total size calculation (CVE-2026-68257)
  * kernel: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists (CVE-2026-68267)
  * kernel: drm/xe: Hold a dma-buf reference for imported BOs (CVE-2026-68266)
  * kernel: drm/amdgpu: Fix context pstate override handling (CVE-2026-68273)
  *…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2026:71700</guid>
    </item>
    <item>
      <title>bdu:2026-05108</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05108</link>
      <description>bdu:2026-05108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05108</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-40323</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-40323</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-2025-40323</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1082 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1082</link>
      <description>certfr-2025-avi-1082</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1082</guid>
    </item>
    <item>
      <title>EUVD-2026-347427</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347427</link>
      <description>EUVD-2026-347427</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347427</guid>
    </item>
    <item>
      <title>fkie_cve-2025-40323</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-40323</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fbcon: Set fb_display[i]-&amp;gt;mode to NULL when the mode is released&lt;/p&gt;
&lt;p&gt;Recently, we discovered the following issue through syzkaller:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0
Read of size 4 at addr ff11000001b3c69c by task syz.xxx
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 dump_stack_lvl+0xab/0xe0
 print_address_description.constprop.0+0x2c/0x390
 print_report+0xb9/0x280
 kasan_report+0xb8/0xf0
 fb_mode_is_equal+0x285/0x2f0
 fbcon_mode_deleted+0x129/0x180
 fb_set_var+0xe7f/0x11d0
 do_fb_ioctl+0x6a0/0x750
 fb_ioctl+0xe0/0x140
 __x64_sys_ioctl+0x193/0x210
 do_syscall_64+0x5f/0x9c0
 entry_SYSCALL_64_after_hwframe+0x76/0x7e&lt;/p&gt;
&lt;p&gt;Based on experimentation and analysis, during framebuffer unregistration,
only the memory of fb_info-&amp;gt;modelist is freed, without setting the
corresponding fb_display[i]-&amp;gt;mode to NULL for the freed modes. This leads
to UAF issues during subsequent accesses. Here&amp;#39;s an example of reproduction
steps:
1. With /dev/fb0 already registered in the system, load a kernel module
   to register a new device /dev/fb1;
2. Set fb1&amp;#39;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);
3. Switch console from fb to VGA (to allow normal rmmod of the ko);
4. Unload the kernel module, at this point fb1&amp;#39;s modelist is freed, leaving
   a wild pointer in fb_display[];
5. Trigger the bug via system calls through fb0 attempting to delete a mode
   from fb0.&lt;/p&gt;
&lt;p&gt;Add a check in do_unregister_framebuffer(): if…&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;fbcon: Set fb_display[i]-&amp;gt;mode to NULL when the mode is released&lt;/p&gt;
&lt;p&gt;Recently, we discovered the following issue through syzkaller:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0
Read of size 4 at addr ff11000001b3c69c by task syz.xxx
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 dump_stack_lvl+0xab/0xe0
 print_address_description.constprop.0+0x2c/0x390
 print_report+0xb9/0x280
 kasan_report+0xb8/0xf0
 fb_mode_is_equal+0x285/0x2f0
 fbcon_mode_deleted+0x129/0x180
 fb_set_var+0xe7f/0x11d0
 do_fb_ioctl+0x6a0/0x750
 fb_ioctl+0xe0/0x140
 __x64_sys_ioctl+0x193/0x210
 do_syscall_64+0x5f/0x9c0
 entry_SYSCALL_64_after_hwframe+0x76/0x7e&lt;/p&gt;
&lt;p&gt;Based on experimentation and analysis, during framebuffer unregistration,
only the memory of fb_info-&amp;gt;modelist is freed, without setting the
corresponding fb_display[i]-&amp;gt;mode to NULL for the freed modes. This leads
to UAF issues during subsequent accesses. Here&amp;#39;s an example of reproduction
steps:
1. With /dev/fb0 already registered in the system, load a kernel module
   to register a new device /dev/fb1;
2. Set fb1&amp;#39;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);
3. Switch console from fb to VGA (to allow normal rmmod of the ko);
4. Unload the kernel module, at this point fb1&amp;#39;s modelist is freed, leaving
   a wild pointer in fb_display[];
5. Trigger the bug via system calls through fb0 attempting to delete a mode
   from fb0.&lt;/p&gt;
&lt;p&gt;Add a check in do_unregister_framebuffer(): if…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-40323</guid>
    </item>
    <item>
      <title>GHSA-vv6w-x7vv-rv35</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vv6w-x7vv-rv35</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fbcon: Set fb_display[i]-&amp;gt;mode to NULL when the mode is released&lt;/p&gt;
&lt;p&gt;Recently, we discovered the following issue through syzkaller:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0
Read of size 4 at addr ff11000001b3c69c by task syz.xxx
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 dump_stack_lvl+0xab/0xe0
 print_address_description.constprop.0+0x2c/0x390
 print_report+0xb9/0x280
 kasan_report+0xb8/0xf0
 fb_mode_is_equal+0x285/0x2f0
 fbcon_mode_deleted+0x129/0x180
 fb_set_var+0xe7f/0x11d0
 do_fb_ioctl+0x6a0/0x750
 fb_ioctl+0xe0/0x140
 __x64_sys_ioctl+0x193/0x210
 do_syscall_64+0x5f/0x9c0
 entry_SYSCALL_64_after_hwframe+0x76/0x7e&lt;/p&gt;
&lt;p&gt;Based on experimentation and analysis, during framebuffer unregistration,
only the memory of fb_info-&amp;gt;modelist is freed, without setting the
corresponding fb_display[i]-&amp;gt;mode to NULL for the freed modes. This leads
to UAF issues during subsequent accesses. Here&amp;#39;s an example of reproduction
steps:
1. With /dev/fb0 already registered in the system, load a kernel module
   to register a new device /dev/fb1;
2. Set fb1&amp;#39;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);
3. Switch console from fb to VGA (to allow normal rmmod of the ko);
4. Unload the kernel module, at this point fb1&amp;#39;s modelist is freed, leaving
   a wild pointer in fb_display[];
5. Trigger the bug via system calls through fb0 attempting to delete a mode
   from fb0.&lt;/p&gt;
&lt;p&gt;Add a check in do_unregister_framebuffer(): if…&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;fbcon: Set fb_display[i]-&amp;gt;mode to NULL when the mode is released&lt;/p&gt;
&lt;p&gt;Recently, we discovered the following issue through syzkaller:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0
Read of size 4 at addr ff11000001b3c69c by task syz.xxx
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 dump_stack_lvl+0xab/0xe0
 print_address_description.constprop.0+0x2c/0x390
 print_report+0xb9/0x280
 kasan_report+0xb8/0xf0
 fb_mode_is_equal+0x285/0x2f0
 fbcon_mode_deleted+0x129/0x180
 fb_set_var+0xe7f/0x11d0
 do_fb_ioctl+0x6a0/0x750
 fb_ioctl+0xe0/0x140
 __x64_sys_ioctl+0x193/0x210
 do_syscall_64+0x5f/0x9c0
 entry_SYSCALL_64_after_hwframe+0x76/0x7e&lt;/p&gt;
&lt;p&gt;Based on experimentation and analysis, during framebuffer unregistration,
only the memory of fb_info-&amp;gt;modelist is freed, without setting the
corresponding fb_display[i]-&amp;gt;mode to NULL for the freed modes. This leads
to UAF issues during subsequent accesses. Here&amp;#39;s an example of reproduction
steps:
1. With /dev/fb0 already registered in the system, load a kernel module
   to register a new device /dev/fb1;
2. Set fb1&amp;#39;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);
3. Switch console from fb to VGA (to allow normal rmmod of the ko);
4. Unload the kernel module, at this point fb1&amp;#39;s modelist is freed, leaving
   a wild pointer in fb_display[];
5. Trigger the bug via system calls through fb0 attempting to delete a mode
   from fb0.&lt;/p&gt;
&lt;p&gt;Add a check in do_unregister_framebuffer(): if…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vv6w-x7vv-rv35</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-40323 — fbcon: Set fb_display[i]-&gt;mode to NULL when the mode is released</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-40323</link>
      <description>msrc_CVE-2025-40323</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-40323</guid>
    </item>
    <item>
      <title>OESA-2026-1566 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-1566</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;udp: Deal with race between UDP socket address change and rehash&lt;/p&gt;
&lt;p&gt;If a UDP socket changes its local address while it&amp;amp;apos;s receiving
datagrams, as a result of connect(), there is a period during which
a lookup operation might fail to find it, after the address is changed
but before the secondary hash (port and address) and the four-tuple
hash (local and remote ports and addresses) are updated.&lt;/p&gt;
&lt;p&gt;Secondary hash chains were introduced by commit 30fff9231fad (&amp;amp;quot;udp:
bind() optimisation&amp;amp;quot;) and, as a result, a rehash operation became
needed to make a bound socket reachable again after a connect().&lt;/p&gt;
&lt;p&gt;This operation was introduced by commit 719f835853a9 (&amp;amp;quot;udp: add
rehash on connect()&amp;amp;quot;) which isn&amp;amp;apos;t however a complete fix: the
socket will be found once the rehashing completes, but not while
it&amp;amp;apos;s pending.&lt;/p&gt;
&lt;p&gt;This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a
client sending datagrams to it. After the server receives the first
datagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to
the address of the sender, in order to set up a directed flow.&lt;/p&gt;
&lt;p&gt;Now, if the client, running on a different CPU thread, happens to
send a (subsequent) datagram while the server&amp;amp;apos;s socket changes its
address, but is not rehashed yet, this will result in a failed
lookup and a port unreachable error delivered to the…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;udp: Deal with race between UDP socket address change and rehash&lt;/p&gt;
&lt;p&gt;If a UDP socket changes its local address while it&amp;amp;apos;s receiving
datagrams, as a result of connect(), there is a period during which
a lookup operation might fail to find it, after the address is changed
but before the secondary hash (port and address) and the four-tuple
hash (local and remote ports and addresses) are updated.&lt;/p&gt;
&lt;p&gt;Secondary hash chains were introduced by commit 30fff9231fad (&amp;amp;quot;udp:
bind() optimisation&amp;amp;quot;) and, as a result, a rehash operation became
needed to make a bound socket reachable again after a connect().&lt;/p&gt;
&lt;p&gt;This operation was introduced by commit 719f835853a9 (&amp;amp;quot;udp: add
rehash on connect()&amp;amp;quot;) which isn&amp;amp;apos;t however a complete fix: the
socket will be found once the rehashing completes, but not while
it&amp;amp;apos;s pending.&lt;/p&gt;
&lt;p&gt;This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a
client sending datagrams to it. After the server receives the first
datagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to
the address of the sender, in order to set up a directed flow.&lt;/p&gt;
&lt;p&gt;Now, if the client, running on a different CPU thread, happens to
send a (subsequent) datagram while the server&amp;amp;apos;s socket changes its
address, but is not rehashed yet, this will result in a failed
lookup and a port unreachable error delivered to the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-1566</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20145-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20145-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/opensuse-su-2026:20145-1</guid>
    </item>
    <item>
      <title>RHSA-2026:71602 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:71602</link>
      <description>&lt;p&gt;kernel: fbcon: Set fb_display[i]-&amp;gt;mode to NULL when the mode is released kernel: libceph: fix potential use-after-free in have_mon_and_osd_map() kernel: libceph: make decode_pool() more resilient against corrupted osdmaps kernel: libceph: prevent potential out-of-bounds reads in handle_auth_done() kernel: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() kernel: Linux kernel: Denial of Service in libceph OSD client due to unreset sparse-read state kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing IB kernel: drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg kernel: drm/amdgpu/userq: fix access to stale wptr mapping kernel: af_unix: Drop all SCM attributes for SOCKMAP kernel: accel/ivpu: Add buffer overflow check in MS get_info_ioctl kernel: drm/xe/eustall: Fix drm_dev_put called before stream disable in close kernel: drm/virtio: use uninterruptible resv lock for plane updates kernel: drm/amdgpu/vce: fix integer overflow in image size kernel: pppoe: reload header pointer after dev_hard_header() kernel: drm/amdkfd: fix 32-bit overflow in CWSR total size calculation kernel: drm/xe: Hold a dma-buf reference for imported BOs kernel: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists kernel: drm/amdgpu: Fix context pstate override handling kernel: ipvs: do not propagate one-packet flag to synced conns kernel: nvme-tcp: fix host memory disclosure on R2T for a read command&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: fbcon: Set fb_display[i]-&amp;gt;mode to NULL when the mode is released kernel: libceph: fix potential use-after-free in have_mon_and_osd_map() kernel: libceph: make decode_pool() more resilient against corrupted osdmaps kernel: libceph: prevent potential out-of-bounds reads in handle_auth_done() kernel: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() kernel: Linux kernel: Denial of Service in libceph OSD client due to unreset sparse-read state kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing IB kernel: drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg kernel: drm/amdgpu/userq: fix access to stale wptr mapping kernel: af_unix: Drop all SCM attributes for SOCKMAP kernel: accel/ivpu: Add buffer overflow check in MS get_info_ioctl kernel: drm/xe/eustall: Fix drm_dev_put called before stream disable in close kernel: drm/virtio: use uninterruptible resv lock for plane updates kernel: drm/amdgpu/vce: fix integer overflow in image size kernel: pppoe: reload header pointer after dev_hard_header() kernel: drm/amdkfd: fix 32-bit overflow in CWSR total size calculation kernel: drm/xe: Hold a dma-buf reference for imported BOs kernel: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists kernel: drm/amdgpu: Fix context pstate override handling kernel: ipvs: do not propagate one-packet flag to synced conns kernel: nvme-tcp: fix host memory disclosure on R2T for a read command&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:71602</guid>
    </item>
    <item>
      <title>RLSA-2026:71602 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rlsa-2026:71602</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: fbcon: Set fb_display[i]-&amp;gt;mode to NULL when the mode is released (CVE-2025-40323)&lt;/p&gt;
&lt;p&gt;* kernel: libceph: fix potential use-after-free in have_mon_and_osd_map() (CVE-2025-68285)&lt;/p&gt;
&lt;p&gt;* kernel: libceph: make decode_pool() more resilient against corrupted osdmaps (CVE-2025-71116)&lt;/p&gt;
&lt;p&gt;* kernel: libceph: prevent potential out-of-bounds reads in handle_auth_done() (CVE-2026-22984)&lt;/p&gt;
&lt;p&gt;* kernel: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (CVE-2026-22990)&lt;/p&gt;
&lt;p&gt;* kernel: Linux kernel: Denial of Service in libceph OSD client due to unreset sparse-read state (CVE-2026-23136)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (CVE-2026-46230)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (CVE-2026-46204)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (CVE-2026-46199)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu/userq: fix access to stale wptr mapping (CVE-2026-46311)&lt;/p&gt;
&lt;p&gt;* kernel: af_unix: Drop all SCM attributes for SOCKMAP (CVE-2026-53005)&lt;/p&gt;
&lt;p&gt;* kernel: accel/ivpu: Add buffer overflow check in MS get_info_ioctl (CVE-2026-53203)&lt;/p&gt;
&lt;p&gt;* kernel: drm/xe/eustall: Fix drm_dev_put called before stream disable in close (CVE-2026-53290)&lt;/p&gt;
&lt;p&gt;* kernel: drm/virtio: use uninterruptible resv lock for plane updates (CVE-2026-64098)&lt;/p&gt;
&lt;p&gt;* kernel: Linux kernel: PPPoE memory corruption via stale pointer (CVE-2026-68121)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu/vce: fix integer overflow in…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: fbcon: Set fb_display[i]-&amp;gt;mode to NULL when the mode is released (CVE-2025-40323)&lt;/p&gt;
&lt;p&gt;* kernel: libceph: fix potential use-after-free in have_mon_and_osd_map() (CVE-2025-68285)&lt;/p&gt;
&lt;p&gt;* kernel: libceph: make decode_pool() more resilient against corrupted osdmaps (CVE-2025-71116)&lt;/p&gt;
&lt;p&gt;* kernel: libceph: prevent potential out-of-bounds reads in handle_auth_done() (CVE-2026-22984)&lt;/p&gt;
&lt;p&gt;* kernel: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (CVE-2026-22990)&lt;/p&gt;
&lt;p&gt;* kernel: Linux kernel: Denial of Service in libceph OSD client due to unreset sparse-read state (CVE-2026-23136)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (CVE-2026-46230)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (CVE-2026-46204)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (CVE-2026-46199)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu/userq: fix access to stale wptr mapping (CVE-2026-46311)&lt;/p&gt;
&lt;p&gt;* kernel: af_unix: Drop all SCM attributes for SOCKMAP (CVE-2026-53005)&lt;/p&gt;
&lt;p&gt;* kernel: accel/ivpu: Add buffer overflow check in MS get_info_ioctl (CVE-2026-53203)&lt;/p&gt;
&lt;p&gt;* kernel: drm/xe/eustall: Fix drm_dev_put called before stream disable in close (CVE-2026-53290)&lt;/p&gt;
&lt;p&gt;* kernel: drm/virtio: use uninterruptible resv lock for plane updates (CVE-2026-64098)&lt;/p&gt;
&lt;p&gt;* kernel: Linux kernel: PPPoE memory corruption via stale pointer (CVE-2026-68121)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu/vce: fix integer overflow in…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rlsa-2026:71602</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0278-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0278-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:0278-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-40323</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40323</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 229 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fbcon: Set fb_display[i]-&amp;gt;mode to NULL when the mode is released Recently, we discovered the following issue through syzkaller: BUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0 Read of size 4 at addr ff11000001b3c69c by task syz.xxx ... Call Trace:  &amp;lt;TASK&amp;gt;  dump_stack_lvl+0xab/0xe0  print_address_description.constprop.0+0x2c/0x390  print_report+0xb9/0x280  kasan_report+0xb8/0xf0  fb_mode_is_equal+0x285/0x2f0  fbcon_mode_deleted+0x129/0x180  fb_set_var+0xe7f/0x11d0  do_fb_ioctl+0x6a0/0x750  fb_ioctl+0xe0/0x140  __x64_sys_ioctl+0x193/0x210  do_syscall_64+0x5f/0x9c0  entry_SYSCALL_64_after_hwframe+0x76/0x7e Based on experimentation and analysis, during framebuffer unregistration, only the memory of fb_info-&amp;gt;modelist is freed, without setting the corresponding fb_display[i]-&amp;gt;mode to NULL for the freed modes. This leads to UAF issues during subsequent accesses. Here&amp;#39;s an example of reproduction steps: 1. With /dev/fb0 already registered in the system, load a kernel module    to register a new device /dev/fb1; 2. Set fb1&amp;#39;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP); 3. Switch console from fb to VGA (to allow normal rmmod of the ko); 4. Unload the kernel module, at this point fb1&amp;#39;s modelist is freed, leaving    a wild pointer in fb_display[]; 5. Trigger the bug via system calls through fb0 attempting to delete a mode    from fb0. Add a check in do_unregister_framebuffer(): if the m…&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 229 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fbcon: Set fb_display[i]-&amp;gt;mode to NULL when the mode is released Recently, we discovered the following issue through syzkaller: BUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0 Read of size 4 at addr ff11000001b3c69c by task syz.xxx ... Call Trace:  &amp;lt;TASK&amp;gt;  dump_stack_lvl+0xab/0xe0  print_address_description.constprop.0+0x2c/0x390  print_report+0xb9/0x280  kasan_report+0xb8/0xf0  fb_mode_is_equal+0x285/0x2f0  fbcon_mode_deleted+0x129/0x180  fb_set_var+0xe7f/0x11d0  do_fb_ioctl+0x6a0/0x750  fb_ioctl+0xe0/0x140  __x64_sys_ioctl+0x193/0x210  do_syscall_64+0x5f/0x9c0  entry_SYSCALL_64_after_hwframe+0x76/0x7e Based on experimentation and analysis, during framebuffer unregistration, only the memory of fb_info-&amp;gt;modelist is freed, without setting the corresponding fb_display[i]-&amp;gt;mode to NULL for the freed modes. This leads to UAF issues during subsequent accesses. Here&amp;#39;s an example of reproduction steps: 1. With /dev/fb0 already registered in the system, load a kernel module    to register a new device /dev/fb1; 2. Set fb1&amp;#39;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP); 3. Switch console from fb to VGA (to allow normal rmmod of the ko); 4. Unload the kernel module, at this point fb1&amp;#39;s modelist is freed, leaving    a wild pointer in fb_display[]; 5. Trigger the bug via system calls through fb0 attempting to delete a mode    from fb0. Add a check in do_unregister_framebuffer(): if the m…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40323</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2756 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2756</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder weitere, nicht spezifizierte Auswirkungen zu erlangen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder weitere, nicht spezifizierte Auswirkungen zu erlangen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2756</guid>
    </item>
  </channel>
</rss>
