<?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>Fri, 20 Nov 2026 18:06:47 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:90365 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:90365</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: udp: Deal with race between UDP socket address change and rehash (CVE-2024-57974)
  * kernel: fuse: re-lock request before replacing page cache folio (CVE-2026-53388)
  * kernel: net/handshake: hand off the pinned file reference to accept_doit (CVE-2026-63979)
  * kernel: net/handshake: Drain pending requests at net namespace exit (CVE-2026-63978)
  * kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)
  * kernel: net/handshake: Take a long-lived file reference at submit (CVE-2026-64523)
  * kernel: ipvs: reload ip header after head reallocation (CVE-2026-68476)
  * kernel: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (CVE-2026-72242)
  * kernel: KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (CVE-2026-74515)
  * kernel: usb: usbfs: fix use-after-free of usb_device in usbdev_release() (CVE-2026-80824)
  * kernel: smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions (CVE-2026-89638)
  * kernel: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure (CVE-2026-89777)
  * kernel: md/raid5-ppl: fix use-after-free in ppl_do_flush() (CVE-2026-93262)
  * kernel: KEYS: encrypted: fix integer overflow of datablob_len (CVE-2026-98222)
  * kernel: netfilter: flowtable: hold reference on ct until flow is released (CVE-2026-98320)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) a…&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: udp: Deal with race between UDP socket address change and rehash (CVE-2024-57974)
  * kernel: fuse: re-lock request before replacing page cache folio (CVE-2026-53388)
  * kernel: net/handshake: hand off the pinned file reference to accept_doit (CVE-2026-63979)
  * kernel: net/handshake: Drain pending requests at net namespace exit (CVE-2026-63978)
  * kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)
  * kernel: net/handshake: Take a long-lived file reference at submit (CVE-2026-64523)
  * kernel: ipvs: reload ip header after head reallocation (CVE-2026-68476)
  * kernel: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (CVE-2026-72242)
  * kernel: KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (CVE-2026-74515)
  * kernel: usb: usbfs: fix use-after-free of usb_device in usbdev_release() (CVE-2026-80824)
  * kernel: smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions (CVE-2026-89638)
  * kernel: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure (CVE-2026-89777)
  * kernel: md/raid5-ppl: fix use-after-free in ppl_do_flush() (CVE-2026-93262)
  * kernel: KEYS: encrypted: fix integer overflow of datablob_len (CVE-2026-98222)
  * kernel: netfilter: flowtable: hold reference on ct until flow is released (CVE-2026-98320)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:90365</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-57974</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-57974</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-2024-57974</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0307 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0307</link>
      <description>certfr-2025-avi-0307</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0307</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:90365 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:90365</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:9: kernel, Rocky Linux:9: kernel-64k, Rocky Linux:9: kernel-64k-core, Rocky Linux:9: kernel-64k-debug, Rocky Linux:9: kernel-64k-debug-core, Rocky Linux:9: kernel-64k-debug-debuginfo, Rocky Linux:9: kernel-rt-core, Rocky Linux:9: kernel-64k-debug-devel, Rocky Linux:9: kernel-64k-debug-devel-matched, Rocky Linux:9: kernel-64k-debuginfo and 79 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: udp: Deal with race between UDP socket address change and rehash (CVE-2024-57974)&lt;/p&gt;
&lt;p&gt;* kernel: fuse: re-lock request before replacing page cache folio (CVE-2026-53388)&lt;/p&gt;
&lt;p&gt;* kernel: net/handshake: hand off the pinned file reference to accept_doit (CVE-2026-63979)&lt;/p&gt;
&lt;p&gt;* kernel: net/handshake: Drain pending requests at net namespace exit (CVE-2026-63978)&lt;/p&gt;
&lt;p&gt;* kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)&lt;/p&gt;
&lt;p&gt;* kernel: net/handshake: Take a long-lived file reference at submit (CVE-2026-64523)&lt;/p&gt;
&lt;p&gt;* kernel: ipvs: reload ip header after head reallocation (CVE-2026-68476)&lt;/p&gt;
&lt;p&gt;* kernel: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (CVE-2026-72242)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (CVE-2026-74515)&lt;/p&gt;
&lt;p&gt;* kernel: usb: usbfs: fix use-after-free of usb_device in usbdev_release() (CVE-2026-80824)&lt;/p&gt;
&lt;p&gt;* kernel: smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions (CVE-2026-89638)&lt;/p&gt;
&lt;p&gt;* kernel: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure (CVE-2026-89777)&lt;/p&gt;
&lt;p&gt;* kernel: md/raid5-ppl: fix use-after-free in ppl_do_flush() (CVE-2026-93262)&lt;/p&gt;
&lt;p&gt;* kernel: KEYS: encrypted: fix integer overflow of datablob_len (CVE-2026-98222)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: flowtable: hold reference on ct until flow is released (CVE-2026-98320)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;*…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:9: kernel, Rocky Linux:9: kernel-64k, Rocky Linux:9: kernel-64k-core, Rocky Linux:9: kernel-64k-debug, Rocky Linux:9: kernel-64k-debug-core, Rocky Linux:9: kernel-64k-debug-debuginfo, Rocky Linux:9: kernel-rt-core, Rocky Linux:9: kernel-64k-debug-devel, Rocky Linux:9: kernel-64k-debug-devel-matched, Rocky Linux:9: kernel-64k-debuginfo and 79 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: udp: Deal with race between UDP socket address change and rehash (CVE-2024-57974)&lt;/p&gt;
&lt;p&gt;* kernel: fuse: re-lock request before replacing page cache folio (CVE-2026-53388)&lt;/p&gt;
&lt;p&gt;* kernel: net/handshake: hand off the pinned file reference to accept_doit (CVE-2026-63979)&lt;/p&gt;
&lt;p&gt;* kernel: net/handshake: Drain pending requests at net namespace exit (CVE-2026-63978)&lt;/p&gt;
&lt;p&gt;* kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)&lt;/p&gt;
&lt;p&gt;* kernel: net/handshake: Take a long-lived file reference at submit (CVE-2026-64523)&lt;/p&gt;
&lt;p&gt;* kernel: ipvs: reload ip header after head reallocation (CVE-2026-68476)&lt;/p&gt;
&lt;p&gt;* kernel: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (CVE-2026-72242)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (CVE-2026-74515)&lt;/p&gt;
&lt;p&gt;* kernel: usb: usbfs: fix use-after-free of usb_device in usbdev_release() (CVE-2026-80824)&lt;/p&gt;
&lt;p&gt;* kernel: smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions (CVE-2026-89638)&lt;/p&gt;
&lt;p&gt;* kernel: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure (CVE-2026-89777)&lt;/p&gt;
&lt;p&gt;* kernel: md/raid5-ppl: fix use-after-free in ppl_do_flush() (CVE-2026-93262)&lt;/p&gt;
&lt;p&gt;* kernel: KEYS: encrypted: fix integer overflow of datablob_len (CVE-2026-98222)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: flowtable: hold reference on ct until flow is released (CVE-2026-98320)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;*…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rlsa-2026:90365</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-57974</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-57974</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 199 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: udp: Deal with race between UDP socket address change and rehash If a UDP socket changes its local address while it&amp;#39;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. Secondary hash chains were introduced by commit 30fff9231fad (&amp;#34;udp: bind() optimisation&amp;#34;) and, as a result, a rehash operation became needed to make a bound socket reachable again after a connect(). This operation was introduced by commit 719f835853a9 (&amp;#34;udp: add rehash on connect()&amp;#34;) which isn&amp;#39;t however a complete fix: the socket will be found once the rehashing completes, but not while it&amp;#39;s pending. 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. Now, if the client, running on a different CPU thread, happens to send a (subsequent) datagram while the server&amp;#39;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 client, as apparent from the following reproducer:   LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4))   dd if=/dev/u…&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 199 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: udp: Deal with race between UDP socket address change and rehash If a UDP socket changes its local address while it&amp;#39;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. Secondary hash chains were introduced by commit 30fff9231fad (&amp;#34;udp: bind() optimisation&amp;#34;) and, as a result, a rehash operation became needed to make a bound socket reachable again after a connect(). This operation was introduced by commit 719f835853a9 (&amp;#34;udp: add rehash on connect()&amp;#34;) which isn&amp;#39;t however a complete fix: the socket will be found once the rehashing completes, but not while it&amp;#39;s pending. 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. Now, if the client, running on a different CPU thread, happens to send a (subsequent) datagram while the server&amp;#39;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 client, as apparent from the following reproducer:   LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4))   dd if=/dev/u…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-57974</guid>
    </item>
  </channel>
</rss>
