<?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>Thu, 19 Nov 2026 20:01:51 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:55764 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:55764</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 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: mm/slub: avoid accessing metadata when pointer is invalid in object_err() (CVE-2025-39902)
  * kernel: drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() (CVE-2026-43206)
  * kernel: crypto: ccp - copy IV using skcipher ivsize (CVE-2026-53016)
  * 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/amdgpu: zero-initialize GART table on allocation (CVE-2026-53374)
  * kernel: drm/i915: Fix potential UAF in TTM object purge (CVE-2026-63884)
  * kernel: drm/amdgpu: fix amdgpu_hmm_range_get_pages (CVE-2026-63879)
  * kernel: drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async (CVE-2026-64219)
  * kernel: can:bcm: arbitrary kernel code execution leading to escalate privileges (CVE-2026-17523)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* Backport &amp;#34;sched/deadline: Fix bandwidth reclaim equation in GRUB&amp;#34; to AlmaLinux 8.10 (JIRA:AlmaLinux-189997)
  * vhost: reset the vring metadata cache on vring reconfiguration [almalinux-8.10.z] (JIRA:AlmaLinux-224556)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 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: mm/slub: avoid accessing metadata when pointer is invalid in object_err() (CVE-2025-39902)
  * kernel: drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() (CVE-2026-43206)
  * kernel: crypto: ccp - copy IV using skcipher ivsize (CVE-2026-53016)
  * 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/amdgpu: zero-initialize GART table on allocation (CVE-2026-53374)
  * kernel: drm/i915: Fix potential UAF in TTM object purge (CVE-2026-63884)
  * kernel: drm/amdgpu: fix amdgpu_hmm_range_get_pages (CVE-2026-63879)
  * kernel: drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async (CVE-2026-64219)
  * kernel: can:bcm: arbitrary kernel code execution leading to escalate privileges (CVE-2026-17523)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* Backport &amp;#34;sched/deadline: Fix bandwidth reclaim equation in GRUB&amp;#34; to AlmaLinux 8.10 (JIRA:AlmaLinux-189997)
  * vhost: reset the vring metadata cache on vring reconfiguration [almalinux-8.10.z] (JIRA:AlmaLinux-224556)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:55764</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-39902</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-39902</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-2025-39902</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0894 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0894</link>
      <description>certfr-2025-avi-0894</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0894</guid>
    </item>
    <item>
      <title>OESA-2026-1566 — kernel security update</title>
      <link>https://127.0.0.1:10001/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://127.0.0.1:10001/vuln/oesa-2026-1566</guid>
    </item>
    <item>
      <title>RLSA-2026:55764 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:55764</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: bpftool, Rocky Linux:8: bpftool-debuginfo, Rocky Linux:8: kernel, Rocky Linux:8: kernel-core, Rocky Linux:8: kernel-debug, Rocky Linux:8: kernel-debug-core, Rocky Linux:8: kernel-debug-debuginfo, Rocky Linux:8: kernel-debug-devel, Rocky Linux:8: kernel-debuginfo, Rocky Linux:8: kernel-debuginfo-common-aarch64 and 16 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: mm/slub: avoid accessing metadata when pointer is invalid in object_err() (CVE-2025-39902)&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: crypto: ccp - copy IV using skcipher ivsize (CVE-2026-53016)&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/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: drm/amdgpu: fix amdgpu_hmm_range_get_pages (CVE-2026-63879)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async (CVE-2026-64219)&lt;/p&gt;
&lt;p&gt;* kernel: can:bcm: arbitrary kernel code execution leading to escalate privileges (CVE-2026-17523)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* Backport &amp;#34;sched/deadline: Fix bandwidth reclaim equation in GRUB&amp;#34; to Rocky Linux 8.10 (JIRA:Rocky Linux-189997)&lt;/p&gt;
&lt;p&gt;* vhost: reset the vring metadata cache on vring reconfiguration [rhel-8.10.z] (JIRA:Rocky Linux-224556)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: bpftool, Rocky Linux:8: bpftool-debuginfo, Rocky Linux:8: kernel, Rocky Linux:8: kernel-core, Rocky Linux:8: kernel-debug, Rocky Linux:8: kernel-debug-core, Rocky Linux:8: kernel-debug-debuginfo, Rocky Linux:8: kernel-debug-devel, Rocky Linux:8: kernel-debuginfo, Rocky Linux:8: kernel-debuginfo-common-aarch64 and 16 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: mm/slub: avoid accessing metadata when pointer is invalid in object_err() (CVE-2025-39902)&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: crypto: ccp - copy IV using skcipher ivsize (CVE-2026-53016)&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/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: drm/amdgpu: fix amdgpu_hmm_range_get_pages (CVE-2026-63879)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async (CVE-2026-64219)&lt;/p&gt;
&lt;p&gt;* kernel: can:bcm: arbitrary kernel code execution leading to escalate privileges (CVE-2026-17523)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* Backport &amp;#34;sched/deadline: Fix bandwidth reclaim equation in GRUB&amp;#34; to Rocky Linux 8.10 (JIRA:Rocky Linux-189997)&lt;/p&gt;
&lt;p&gt;* vhost: reset the vring metadata cache on vring reconfiguration [rhel-8.10.z] (JIRA:Rocky Linux-224556)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rlsa-2026:55764</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39902</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39902</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 216 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/slub: avoid accessing metadata when pointer is invalid in object_err() object_err() reports details of an object for further debugging, such as the freelist pointer, redzone, etc. However, if the pointer is invalid, attempting to access object metadata can lead to a crash since it does not point to a valid object. One known path to the crash is when alloc_consistency_checks() determines the pointer to the allocated object is invalid because of a freelist corruption, and calls object_err() to report it. The debug code should report and handle the corruption gracefully and not crash in the process. In case the pointer is NULL or check_valid_pointer() returns false for the pointer, only print the pointer value and skip accessing metadata.&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 216 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/slub: avoid accessing metadata when pointer is invalid in object_err() object_err() reports details of an object for further debugging, such as the freelist pointer, redzone, etc. However, if the pointer is invalid, attempting to access object metadata can lead to a crash since it does not point to a valid object. One known path to the crash is when alloc_consistency_checks() determines the pointer to the allocated object is invalid because of a freelist corruption, and calls object_err() to report it. The debug code should report and handle the corruption gracefully and not crash in the process. In case the pointer is NULL or check_valid_pointer() returns false for the pointer, only print the pointer value and skip accessing metadata.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39902</guid>
    </item>
  </channel>
</rss>
