<?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 23:50:05 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:57251 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2026:57251</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 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: drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() (CVE-2026-43206)
  * kernel: drm/amdgpu: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4 (CVE-2026-43237)
  * kernel: crypto: pcrypt - Fix handling of MAY_BACKLOG requests (CVE-2026-43493)
  * kernel: udf: fix partition descriptor append bookkeeping (CVE-2026-45991)
  * kernel: drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 (CVE-2026-45878)
  * kernel: smb/client: fix out-of-bounds read in symlink_data() (CVE-2026-46185)
  * kernel: sched/psi: fix race between file release and pressure write (CVE-2026-52991)
  * kernel: drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 (CVE-2026-53143)
  * kernel: drm/amd/display: Clamp VBIOS HDMI retimer register count to array size (CVE-2026-53136)
  * kernel: drm/amd/display: Use krealloc_array() in dal_vector_reserve() (CVE-2026-53329)
  * kernel: drm/i915/gem: Fix phys BO pread/pwrite with offset (CVE-2026-53356)
  * kernel: drm/amdgpu: zero-initialize GART table on allocation (CVE-2026-53374)
  * kernel: drm/i915: Fix potential UAF in TTM object purge (CVE-2026-63884)
  * kernel: scsi: target: iscsi: Validate CHAP_R length before base64 decode (CVE-2026-63886)
  * kernel: memfd: deny writeable mappings when implying SEAL_WRITE (CVE-2026-63952)
  * kernel: scsi: target: iscsi:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 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: drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() (CVE-2026-43206)
  * kernel: drm/amdgpu: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4 (CVE-2026-43237)
  * kernel: crypto: pcrypt - Fix handling of MAY_BACKLOG requests (CVE-2026-43493)
  * kernel: udf: fix partition descriptor append bookkeeping (CVE-2026-45991)
  * kernel: drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 (CVE-2026-45878)
  * kernel: smb/client: fix out-of-bounds read in symlink_data() (CVE-2026-46185)
  * kernel: sched/psi: fix race between file release and pressure write (CVE-2026-52991)
  * kernel: drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 (CVE-2026-53143)
  * kernel: drm/amd/display: Clamp VBIOS HDMI retimer register count to array size (CVE-2026-53136)
  * kernel: drm/amd/display: Use krealloc_array() in dal_vector_reserve() (CVE-2026-53329)
  * kernel: drm/i915/gem: Fix phys BO pread/pwrite with offset (CVE-2026-53356)
  * kernel: drm/amdgpu: zero-initialize GART table on allocation (CVE-2026-53374)
  * kernel: drm/i915: Fix potential UAF in TTM object purge (CVE-2026-63884)
  * kernel: scsi: target: iscsi: Validate CHAP_R length before base64 decode (CVE-2026-63886)
  * kernel: memfd: deny writeable mappings when implying SEAL_WRITE (CVE-2026-63952)
  * kernel: scsi: target: iscsi:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2026:57251</guid>
    </item>
    <item>
      <title>bdu:2026-13940</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-13940</link>
      <description>bdu:2026-13940</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-13940</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-52991</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-52991</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-52991</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://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>EUVD-2026-356626</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-356626</link>
      <description>EUVD-2026-356626</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-356626</guid>
    </item>
    <item>
      <title>fkie_cve-2026-52991</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-52991</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched/psi: fix race between file release and pressure write&lt;/p&gt;
&lt;p&gt;A potential race condition exists between pressure write and cgroup file
release regarding the priv member of struct kernfs_open_file, which
triggers the uaf reported in [1].&lt;/p&gt;
&lt;p&gt;Consider the following scenario involving execution on two separate CPUs:&lt;/p&gt;
&lt;p&gt;CPU0					CPU1
   ====					====
					vfs_rmdir()
					kernfs_iop_rmdir()
					cgroup_rmdir()
					cgroup_kn_lock_live()
					cgroup_destroy_locked()
					cgroup_addrm_files()
					cgroup_rm_file()
					kernfs_remove_by_name()
					kernfs_remove_by_name_ns()
 vfs_write()				__kernfs_remove()
 new_sync_write()			kernfs_drain()
 kernfs_fop_write_iter()		kernfs_drain_open_files()
 cgroup_file_write()			kernfs_release_file()
 pressure_write()			cgroup_file_release()
 ctx = of-&amp;gt;priv;
					kfree(ctx);
 					of-&amp;gt;priv = NULL;
					cgroup_kn_unlock()
 cgroup_kn_lock_live()
 cgroup_get(cgrp)
 cgroup_kn_unlock()
 if (ctx-&amp;gt;psi.trigger)  // here, trigger uaf for ctx, that is of-&amp;gt;priv&lt;/p&gt;
&lt;p&gt;The cgroup_rmdir() is protected by the cgroup_mutex, it also safeguards
the memory deallocation of of-&amp;gt;priv performed within cgroup_file_release().
However, the operations involving of-&amp;gt;priv executed within pressure_write()
are not entirely covered by the protection of cgroup_mutex. Consequently,
if the code in pressure_write(), specifically the section handling the
ctx variable executes after cgroup_file_release() has completed, a…&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;sched/psi: fix race between file release and pressure write&lt;/p&gt;
&lt;p&gt;A potential race condition exists between pressure write and cgroup file
release regarding the priv member of struct kernfs_open_file, which
triggers the uaf reported in [1].&lt;/p&gt;
&lt;p&gt;Consider the following scenario involving execution on two separate CPUs:&lt;/p&gt;
&lt;p&gt;CPU0					CPU1
   ====					====
					vfs_rmdir()
					kernfs_iop_rmdir()
					cgroup_rmdir()
					cgroup_kn_lock_live()
					cgroup_destroy_locked()
					cgroup_addrm_files()
					cgroup_rm_file()
					kernfs_remove_by_name()
					kernfs_remove_by_name_ns()
 vfs_write()				__kernfs_remove()
 new_sync_write()			kernfs_drain()
 kernfs_fop_write_iter()		kernfs_drain_open_files()
 cgroup_file_write()			kernfs_release_file()
 pressure_write()			cgroup_file_release()
 ctx = of-&amp;gt;priv;
					kfree(ctx);
 					of-&amp;gt;priv = NULL;
					cgroup_kn_unlock()
 cgroup_kn_lock_live()
 cgroup_get(cgrp)
 cgroup_kn_unlock()
 if (ctx-&amp;gt;psi.trigger)  // here, trigger uaf for ctx, that is of-&amp;gt;priv&lt;/p&gt;
&lt;p&gt;The cgroup_rmdir() is protected by the cgroup_mutex, it also safeguards
the memory deallocation of of-&amp;gt;priv performed within cgroup_file_release().
However, the operations involving of-&amp;gt;priv executed within pressure_write()
are not entirely covered by the protection of cgroup_mutex. Consequently,
if the code in pressure_write(), specifically the section handling the
ctx variable executes after cgroup_file_release() has completed, a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-52991</guid>
    </item>
    <item>
      <title>GHSA-3v2r-c9x3-5fgr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3v2r-c9x3-5fgr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched/psi: fix race between file release and pressure write&lt;/p&gt;
&lt;p&gt;A potential race condition exists between pressure write and cgroup file
release regarding the priv member of struct kernfs_open_file, which
triggers the uaf reported in [1].&lt;/p&gt;
&lt;p&gt;Consider the following scenario involving execution on two separate CPUs:&lt;/p&gt;
&lt;p&gt;CPU0					CPU1
   ====					====
					vfs_rmdir()
					kernfs_iop_rmdir()
					cgroup_rmdir()
					cgroup_kn_lock_live()
					cgroup_destroy_locked()
					cgroup_addrm_files()
					cgroup_rm_file()
					kernfs_remove_by_name()
					kernfs_remove_by_name_ns()
 vfs_write()				__kernfs_remove()
 new_sync_write()			kernfs_drain()
 kernfs_fop_write_iter()		kernfs_drain_open_files()
 cgroup_file_write()			kernfs_release_file()
 pressure_write()			cgroup_file_release()
 ctx = of-&amp;gt;priv;
					kfree(ctx);
 					of-&amp;gt;priv = NULL;
					cgroup_kn_unlock()
 cgroup_kn_lock_live()
 cgroup_get(cgrp)
 cgroup_kn_unlock()
 if (ctx-&amp;gt;psi.trigger)  // here, trigger uaf for ctx, that is of-&amp;gt;priv&lt;/p&gt;
&lt;p&gt;The cgroup_rmdir() is protected by the cgroup_mutex, it also safeguards
the memory deallocation of of-&amp;gt;priv performed within cgroup_file_release().
However, the operations involving of-&amp;gt;priv executed within pressure_write()
are not entirely covered by the protection of cgroup_mutex. Consequently,
if the code in pressure_write(), specifically the section handling the
ctx variable executes after cgroup_file_release() has completed, a…&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;sched/psi: fix race between file release and pressure write&lt;/p&gt;
&lt;p&gt;A potential race condition exists between pressure write and cgroup file
release regarding the priv member of struct kernfs_open_file, which
triggers the uaf reported in [1].&lt;/p&gt;
&lt;p&gt;Consider the following scenario involving execution on two separate CPUs:&lt;/p&gt;
&lt;p&gt;CPU0					CPU1
   ====					====
					vfs_rmdir()
					kernfs_iop_rmdir()
					cgroup_rmdir()
					cgroup_kn_lock_live()
					cgroup_destroy_locked()
					cgroup_addrm_files()
					cgroup_rm_file()
					kernfs_remove_by_name()
					kernfs_remove_by_name_ns()
 vfs_write()				__kernfs_remove()
 new_sync_write()			kernfs_drain()
 kernfs_fop_write_iter()		kernfs_drain_open_files()
 cgroup_file_write()			kernfs_release_file()
 pressure_write()			cgroup_file_release()
 ctx = of-&amp;gt;priv;
					kfree(ctx);
 					of-&amp;gt;priv = NULL;
					cgroup_kn_unlock()
 cgroup_kn_lock_live()
 cgroup_get(cgrp)
 cgroup_kn_unlock()
 if (ctx-&amp;gt;psi.trigger)  // here, trigger uaf for ctx, that is of-&amp;gt;priv&lt;/p&gt;
&lt;p&gt;The cgroup_rmdir() is protected by the cgroup_mutex, it also safeguards
the memory deallocation of of-&amp;gt;priv performed within cgroup_file_release().
However, the operations involving of-&amp;gt;priv executed within pressure_write()
are not entirely covered by the protection of cgroup_mutex. Consequently,
if the code in pressure_write(), specifically the section handling the
ctx variable executes after cgroup_file_release() has completed, a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3v2r-c9x3-5fgr</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-52991 — sched/psi: fix race between file release and pressure write</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-52991</link>
      <description>msrc_CVE-2026-52991</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-52991</guid>
    </item>
    <item>
      <title>OESA-2026-2930 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-2930</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: 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;wifi: mac80211: check tdls flag in ieee80211_tdls_oper&lt;/p&gt;
&lt;p&gt;When NL80211_TDLS_ENABLE_LINK is called, the code only checks if the
station exists but not whether it is actually a TDLS station. This
allows the operation to proceed for non-TDLS stations, causing
unintended side effects like modifying channel context and HT
protection before failing.&lt;/p&gt;
&lt;p&gt;Add a check for sta-&amp;amp;gt;sta.tdls early in the ENABLE_LINK case, before
any side effects occur, to ensure the operation is only allowed for
actual TDLS peers.(CVE-2026-43052)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: brcmfmac: validate bsscfg indices in IF events&lt;/p&gt;
&lt;p&gt;brcmf_fweh_handle_if_event() validates the firmware-provided interface
index before it touches drvr-&amp;amp;gt;iflist[], but it still uses the raw
bsscfgidx field as an array index without a matching range check.&lt;/p&gt;
&lt;p&gt;Reject IF events whose bsscfg index does not fit in drvr-&amp;amp;gt;iflist[]
before indexing the interface array.&lt;/p&gt;
&lt;p&gt;[add missing wifi prefix](CVE-2026-43110)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: roccat: fix use-after-free in roccat_report_event&lt;/p&gt;
&lt;p&gt;roccat_report_event() iterates over the device-&amp;amp;gt;readers list without
holding the readers_lock. This allows a concurrent roccat_release() to
remove and free a reader while it&amp;amp;apos;s still being accessed, leading to a
use-after-f…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: 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;wifi: mac80211: check tdls flag in ieee80211_tdls_oper&lt;/p&gt;
&lt;p&gt;When NL80211_TDLS_ENABLE_LINK is called, the code only checks if the
station exists but not whether it is actually a TDLS station. This
allows the operation to proceed for non-TDLS stations, causing
unintended side effects like modifying channel context and HT
protection before failing.&lt;/p&gt;
&lt;p&gt;Add a check for sta-&amp;amp;gt;sta.tdls early in the ENABLE_LINK case, before
any side effects occur, to ensure the operation is only allowed for
actual TDLS peers.(CVE-2026-43052)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: brcmfmac: validate bsscfg indices in IF events&lt;/p&gt;
&lt;p&gt;brcmf_fweh_handle_if_event() validates the firmware-provided interface
index before it touches drvr-&amp;amp;gt;iflist[], but it still uses the raw
bsscfgidx field as an array index without a matching range check.&lt;/p&gt;
&lt;p&gt;Reject IF events whose bsscfg index does not fit in drvr-&amp;amp;gt;iflist[]
before indexing the interface array.&lt;/p&gt;
&lt;p&gt;[add missing wifi prefix](CVE-2026-43110)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: roccat: fix use-after-free in roccat_report_event&lt;/p&gt;
&lt;p&gt;roccat_report_event() iterates over the device-&amp;amp;gt;readers list without
holding the readers_lock. This allows a concurrent roccat_release() to
remove and free a reader while it&amp;amp;apos;s still being accessed, leading to a
use-after-f…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-2930</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21910-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-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:21910-1</guid>
    </item>
    <item>
      <title>RHSA-2026:57254 — Red Hat Security Advisory: kernel-rt security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:57254</link>
      <description>&lt;p&gt;kernel: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() kernel: ip6_gre: Use cached t-&amp;gt;net in ip6erspan_changelink() kernel: sched/psi: fix race between file release and pressure write kernel: mm/huge_memory: update file PMD counter before folio_put() kernel: scsi: target: iscsi: Bound iscsi_encode_text_output() appends to rsp_buf kernel: scsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd() kernel: net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot kernel: smb: client: mask server-provided mode to 07777 in modefromsid kernel: smb/client: handle overlapping allocated ranges in fallocate&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() kernel: ip6_gre: Use cached t-&amp;gt;net in ip6erspan_changelink() kernel: sched/psi: fix race between file release and pressure write kernel: mm/huge_memory: update file PMD counter before folio_put() kernel: scsi: target: iscsi: Bound iscsi_encode_text_output() appends to rsp_buf kernel: scsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd() kernel: net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot kernel: smb: client: mask server-provided mode to 07777 in modefromsid kernel: smb/client: handle overlapping allocated ranges in fallocate&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:57254</guid>
    </item>
    <item>
      <title>RLSA-2026:57251 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rlsa-2026:57251</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: drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() (CVE-2026-43206)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4 (CVE-2026-43237)&lt;/p&gt;
&lt;p&gt;* kernel: crypto: pcrypt - Fix handling of MAY_BACKLOG requests (CVE-2026-43493)&lt;/p&gt;
&lt;p&gt;* kernel: udf: fix partition descriptor append bookkeeping (CVE-2026-45991)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 (CVE-2026-45878)&lt;/p&gt;
&lt;p&gt;* kernel: smb/client: fix out-of-bounds read in symlink_data() (CVE-2026-46185)&lt;/p&gt;
&lt;p&gt;* kernel: sched/psi: fix race between file release and pressure write (CVE-2026-52991)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 (CVE-2026-53143)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amd/display: Clamp VBIOS HDMI retimer register count to array size (CVE-2026-53136)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amd/display: Use krealloc_array() in dal_vector_reserve() (CVE-2026-53329)&lt;/p&gt;
&lt;p&gt;* kernel: drm/i915/gem: Fix phys BO pread/pwrite with offset (CVE-2026-53356)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu: zero-initialize GART table on allocation (CVE-2026-53374)&lt;/p&gt;
&lt;p&gt;* kernel: drm/i915: Fix potential UAF in TTM object purge (CVE-2026-63884)&lt;/p&gt;
&lt;p&gt;* kernel: scsi: target: iscsi: Validate CHAP_R length before base64 decode (CVE-2026-63886)&lt;/p&gt;
&lt;p&gt;* kernel: memfd: deny writeable mappings when implying SEAL_WRITE (CVE-2026-63952)&lt;/p&gt;
&lt;p&gt;* kernel: scsi: target: iscsi: Fix CRC overread and…&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: drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() (CVE-2026-43206)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4 (CVE-2026-43237)&lt;/p&gt;
&lt;p&gt;* kernel: crypto: pcrypt - Fix handling of MAY_BACKLOG requests (CVE-2026-43493)&lt;/p&gt;
&lt;p&gt;* kernel: udf: fix partition descriptor append bookkeeping (CVE-2026-45991)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 (CVE-2026-45878)&lt;/p&gt;
&lt;p&gt;* kernel: smb/client: fix out-of-bounds read in symlink_data() (CVE-2026-46185)&lt;/p&gt;
&lt;p&gt;* kernel: sched/psi: fix race between file release and pressure write (CVE-2026-52991)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 (CVE-2026-53143)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amd/display: Clamp VBIOS HDMI retimer register count to array size (CVE-2026-53136)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amd/display: Use krealloc_array() in dal_vector_reserve() (CVE-2026-53329)&lt;/p&gt;
&lt;p&gt;* kernel: drm/i915/gem: Fix phys BO pread/pwrite with offset (CVE-2026-53356)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu: zero-initialize GART table on allocation (CVE-2026-53374)&lt;/p&gt;
&lt;p&gt;* kernel: drm/i915: Fix potential UAF in TTM object purge (CVE-2026-63884)&lt;/p&gt;
&lt;p&gt;* kernel: scsi: target: iscsi: Validate CHAP_R length before base64 decode (CVE-2026-63886)&lt;/p&gt;
&lt;p&gt;* kernel: memfd: deny writeable mappings when implying SEAL_WRITE (CVE-2026-63952)&lt;/p&gt;
&lt;p&gt;* kernel: scsi: target: iscsi: Fix CRC overread and…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rlsa-2026:57251</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23193-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23193-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:23193-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-52991</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-52991</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 227 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/psi: fix race between file release and pressure write A potential race condition exists between pressure write and cgroup file release regarding the priv member of struct kernfs_open_file, which triggers the uaf reported in [1]. Consider the following scenario involving execution on two separate CPUs:    CPU0					CPU1    ====					==== 					vfs_rmdir() 					kernfs_iop_rmdir() 					cgroup_rmdir() 					cgroup_kn_lock_live() 					cgroup_destroy_locked() 					cgroup_addrm_files() 					cgroup_rm_file() 					kernfs_remove_by_name() 					kernfs_remove_by_name_ns()  vfs_write()				__kernfs_remove()  new_sync_write()			kernfs_drain()  kernfs_fop_write_iter()		kernfs_drain_open_files()  cgroup_file_write()			kernfs_release_file()  pressure_write()			cgroup_file_release()  ctx = of-&amp;gt;priv; 					kfree(ctx);  					of-&amp;gt;priv = NULL; 					cgroup_kn_unlock()  cgroup_kn_lock_live()  cgroup_get(cgrp)  cgroup_kn_unlock()  if (ctx-&amp;gt;psi.trigger)  // here, trigger uaf for ctx, that is of-&amp;gt;priv The cgroup_rmdir() is protected by the cgroup_mutex, it also safeguards the memory deallocation of of-&amp;gt;priv performed within cgroup_file_release(). However, the operations involving of-&amp;gt;priv executed within pressure_write() are not entirely covered by the protection of cgroup_mutex. Consequently, if the code in pressure_write(), specifically the section handling the ctx variable executes after cgroup_file_release() has completed, a uaf v…&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 227 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/psi: fix race between file release and pressure write A potential race condition exists between pressure write and cgroup file release regarding the priv member of struct kernfs_open_file, which triggers the uaf reported in [1]. Consider the following scenario involving execution on two separate CPUs:    CPU0					CPU1    ====					==== 					vfs_rmdir() 					kernfs_iop_rmdir() 					cgroup_rmdir() 					cgroup_kn_lock_live() 					cgroup_destroy_locked() 					cgroup_addrm_files() 					cgroup_rm_file() 					kernfs_remove_by_name() 					kernfs_remove_by_name_ns()  vfs_write()				__kernfs_remove()  new_sync_write()			kernfs_drain()  kernfs_fop_write_iter()		kernfs_drain_open_files()  cgroup_file_write()			kernfs_release_file()  pressure_write()			cgroup_file_release()  ctx = of-&amp;gt;priv; 					kfree(ctx);  					of-&amp;gt;priv = NULL; 					cgroup_kn_unlock()  cgroup_kn_lock_live()  cgroup_get(cgrp)  cgroup_kn_unlock()  if (ctx-&amp;gt;psi.trigger)  // here, trigger uaf for ctx, that is of-&amp;gt;priv The cgroup_rmdir() is protected by the cgroup_mutex, it also safeguards the memory deallocation of of-&amp;gt;priv performed within cgroup_file_release(). However, the operations involving of-&amp;gt;priv executed within pressure_write() are not entirely covered by the protection of cgroup_mutex. Consequently, if the code in pressure_write(), specifically the section handling the ctx variable executes after cgroup_file_release() has completed, a uaf v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-52991</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2077 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</link>
      <description>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</guid>
    </item>
  </channel>
</rss>
