<?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://127.0.0.1:10001</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, 21 Nov 2026 04:08:44 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:57251 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:57251</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&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-abi-stablelists, AlmaLinux:10: kernel-doc&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://127.0.0.1:10001/vuln/alsa-2026:57251</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-64560</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64560</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://127.0.0.1:10001/vuln/bell-cve-2026-64560</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0981 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0981</link>
      <description>certfr-2026-avi-0981</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0981</guid>
    </item>
    <item>
      <title>OESA-2026-3303 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3303</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;comedi: me4000: Fix potential overrun of firmware buffer&lt;/p&gt;
&lt;p&gt;`me4000_xilinx_download()` loads the firmware that was requested by
`request_firmware()`.  It is possible for it to overrun the source
buffer because it blindly trusts the file format.  It reads a data
stream length from the first 4 bytes into variable `file_length` and
reads the data stream contents of length `file_length` from offset 16
onwards.&lt;/p&gt;
&lt;p&gt;Add a test to ensure that the supplied firmware is long enough to
contain the header and the data stream.  On failure, log an error and
return `-EINVAL`.&lt;/p&gt;
&lt;p&gt;Note: The firmware loading was totally broken before commit ac584af59945
(&amp;amp;quot;staging: comedi: me4000: fix firmware downloading&amp;amp;quot;), but that is the
most sensible target for this fix.(CVE-2026-31747)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ASoC: soc-core: flush delayed work before removing DAIs and widgets&lt;/p&gt;
&lt;p&gt;When a sound card is unbound while a PCM stream is open, a
use-after-free can occur in snd_soc_dapm_stream_event(), called from
the close_delayed_work workqueue handler.&lt;/p&gt;
&lt;p&gt;During unbind, snd_soc_unbind_card() flushes delayed work and then
calls soc_cleanup_card_resources(). Inside cleanup,
snd_card_disconnect_sync() releases all PCM file descriptors, and
the resulting PCM close path can call snd_soc_dapm_stream_stop()
which schedules new delayed…&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;comedi: me4000: Fix potential overrun of firmware buffer&lt;/p&gt;
&lt;p&gt;`me4000_xilinx_download()` loads the firmware that was requested by
`request_firmware()`.  It is possible for it to overrun the source
buffer because it blindly trusts the file format.  It reads a data
stream length from the first 4 bytes into variable `file_length` and
reads the data stream contents of length `file_length` from offset 16
onwards.&lt;/p&gt;
&lt;p&gt;Add a test to ensure that the supplied firmware is long enough to
contain the header and the data stream.  On failure, log an error and
return `-EINVAL`.&lt;/p&gt;
&lt;p&gt;Note: The firmware loading was totally broken before commit ac584af59945
(&amp;amp;quot;staging: comedi: me4000: fix firmware downloading&amp;amp;quot;), but that is the
most sensible target for this fix.(CVE-2026-31747)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ASoC: soc-core: flush delayed work before removing DAIs and widgets&lt;/p&gt;
&lt;p&gt;When a sound card is unbound while a PCM stream is open, a
use-after-free can occur in snd_soc_dapm_stream_event(), called from
the close_delayed_work workqueue handler.&lt;/p&gt;
&lt;p&gt;During unbind, snd_soc_unbind_card() flushes delayed work and then
calls soc_cleanup_card_resources(). Inside cleanup,
snd_card_disconnect_sync() releases all PCM file descriptors, and
the resulting PCM close path can call snd_soc_dapm_stream_stop()
which schedules new delayed…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3303</guid>
    </item>
    <item>
      <title>RLSA-2026:57251 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:57251</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: libperf, Rocky Linux:10: kernel-64k-debuginfo, Rocky Linux:10: kernel-uki-virt-addons, Rocky Linux:10: kernel-debug-devel-matched, Rocky Linux:10: kernel-modules, Rocky Linux:10: kernel-tools-debuginfo, Rocky Linux:10: kernel-rt, Rocky Linux:10: kernel-64k-debug-modules-extra, Rocky Linux:10: kernel-rt-64k-modules-core, Rocky Linux:10: rv and 69 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)&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: libperf, Rocky Linux:10: kernel-64k-debuginfo, Rocky Linux:10: kernel-uki-virt-addons, Rocky Linux:10: kernel-debug-devel-matched, Rocky Linux:10: kernel-modules, Rocky Linux:10: kernel-tools-debuginfo, Rocky Linux:10: kernel-rt, Rocky Linux:10: kernel-64k-debug-modules-extra, Rocky Linux:10: kernel-rt-64k-modules-core, Rocky Linux:10: rv and 69 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)&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://127.0.0.1:10001/vuln/rlsa-2026:57251</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64560</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64560</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Prevent UAF caused by non-leader exec() race Wongi and Jungwoo decoded and reported a non-leader exec() related race which can result in an UAF:  sys_timer_delete()			exec()    posix_cpu_timer_del()    // Observes old leader    p = pid_task(pid, pid_type);		de_thread()    					  switch_leader(); 					  release_task(old_leader) 					    __exit_signal(old_leader) 					      sighand = lock(old_leader, sighand); 					      posix_cpu_timers*_exit();    sighand = lock_task_sighand(p)	      unhash_task(old_leader);      sh = lock(p, sighand)	    	      old_leader-&amp;gt;sighand = NULL; 					      unlock(sighand);      (p-&amp;gt;sighand == NULL) 	unlock(sh) 	return NULL;    // Returns without action    if(!sighand)       return 0;    free_posix_timer(); This is &amp;#34;harmless&amp;#34; unless the deleted timer was armed and enqueued in p-&amp;gt;signal because on exec() a TGID targeted timer is inherited. As sys_timer_delete() freed the underlying posix timer object run_posix_cpu_timers() or any timerqueue related add/delete operations on other timers will access the freed object&amp;#39;s timerqueue node, which results in an UAF. There is a similar problem vs. posix_cpu_timer_set(). For regular posix timers it just transiently returns -ESRCH to user space, but for the use case in do_cpu_nanosleep() it&amp;#39;s the same UAF just that the k_itimer is allocated on the stack. Also posix_cpu_timer_rearm() fails to rearm the timer, which means it sto…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Prevent UAF caused by non-leader exec() race Wongi and Jungwoo decoded and reported a non-leader exec() related race which can result in an UAF:  sys_timer_delete()			exec()    posix_cpu_timer_del()    // Observes old leader    p = pid_task(pid, pid_type);		de_thread()    					  switch_leader(); 					  release_task(old_leader) 					    __exit_signal(old_leader) 					      sighand = lock(old_leader, sighand); 					      posix_cpu_timers*_exit();    sighand = lock_task_sighand(p)	      unhash_task(old_leader);      sh = lock(p, sighand)	    	      old_leader-&amp;gt;sighand = NULL; 					      unlock(sighand);      (p-&amp;gt;sighand == NULL) 	unlock(sh) 	return NULL;    // Returns without action    if(!sighand)       return 0;    free_posix_timer(); This is &amp;#34;harmless&amp;#34; unless the deleted timer was armed and enqueued in p-&amp;gt;signal because on exec() a TGID targeted timer is inherited. As sys_timer_delete() freed the underlying posix timer object run_posix_cpu_timers() or any timerqueue related add/delete operations on other timers will access the freed object&amp;#39;s timerqueue node, which results in an UAF. There is a similar problem vs. posix_cpu_timer_set(). For regular posix timers it just transiently returns -ESRCH to user space, but for the use case in do_cpu_nanosleep() it&amp;#39;s the same UAF just that the k_itimer is allocated on the stack. Also posix_cpu_timer_rearm() fails to rearm the timer, which means it sto…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64560</guid>
    </item>
  </channel>
</rss>
