<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T15:12:24.216857+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/alsa-2026:90365</id>
    <title>ALSA-2026:90365 — Important: kernel security, bug fix, and enhancement update</title>
    <updated>2026-11-21T15:12:24.222945+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>* 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-&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)</p>
<p>Bug Fix(es) a…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2026:90365"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-64523</id>
    <title>BELL-CVE-2026-64523</title>
    <updated>2026-11-21T15:12:24.223015+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-64523"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0954</id>
    <title>certfr-2026-avi-0954 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-11-21T15:12:24.223025+00:00</updated>
    <content>certfr-2026-avi-0954</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0954"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-3707</id>
    <title>OESA-2026-3707 — kernel security update</title>
    <updated>2026-11-21T15:12:24.223032+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>seg6: separate dst_cache for input and output paths in seg6 lwtunnel</p>
<p>The seg6 lwtunnel uses a single dst_cache per encap route, shared
between seg6_input_core() and seg6_output_core(). These two paths
can perform the post-encap SID lookup in different routing contexts
(e.g., ip rules matching on the ingress interface, or VRF table
separation). Whichever path runs first populates the cache, and the
other reuses it blindly, bypassing its own lookup.</p>
<p>Fix this by splitting the cache into cache_input and cache_output,
so each path maintains its own cached dst independently.(CVE-2026-31668)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>RDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE</p>
<p>The current implementation incorrectly handles memory regions (MRs) with
page sizes different from the system PAGE_SIZE. The core issue is that
rxe_set_page() is called with mr-&amp;gt;page_size step increments, but the
page_list stores individual struct page pointers, each representing
PAGE_SIZE of memory.</p>
<p>ib_sg_to_page() has ensured that when i&amp;gt;=1 either
a) SG[i-1].dma_end and SG[i].dma_addr are contiguous
or
b) SG[i-1].dma_end and SG[i].dma_addr are mr-&amp;gt;page_size aligned.</p>
<p>This leads to incorrect iova-to-va conversion in scenarios:</p>
<p>1) page_size &amp;lt; PAGE_SIZE (e.g., MR: 4K, system: 64K):
   ibmr-&amp;gt;iova = 0x1…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-3707"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rlsa-2026:90365</id>
    <title>RLSA-2026:90365 — Important: kernel security, bug fix, and enhancement update</title>
    <updated>2026-11-21T15:12:24.223353+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>* kernel: udp: Deal with race between UDP socket address change and rehash (CVE-2024-57974)</p>
<p>* kernel: fuse: re-lock request before replacing page cache folio (CVE-2026-53388)</p>
<p>* kernel: net/handshake: hand off the pinned file reference to accept_doit (CVE-2026-63979)</p>
<p>* kernel: net/handshake: Drain pending requests at net namespace exit (CVE-2026-63978)</p>
<p>* kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)</p>
<p>* kernel: net/handshake: Take a long-lived file reference at submit (CVE-2026-64523)</p>
<p>* kernel: ipvs: reload ip header after head reallocation (CVE-2026-68476)</p>
<p>* kernel: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (CVE-2026-72242)</p>
<p>* kernel: KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (CVE-2026-74515)</p>
<p>* kernel: usb: usbfs: fix use-after-free of usb_device in usbdev_release() (CVE-2026-80824)</p>
<p>* kernel: smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions (CVE-2026-89638)</p>
<p>* kernel: vfio/pci: clear vdev-&gt;msi_perm after freeing it on init failure (CVE-2026-89777)</p>
<p>* kernel: md/raid5-ppl: fix use-after-free in ppl_do_flush() (CVE-2026-93262)</p>
<p>* kernel: KEYS: encrypted: fix integer overflow of datablob_len (CVE-2026-98222)</p>
<p>* kernel: netfilter: flowtable: hold reference on ct until flow is released (CVE-2026-98320)</p>
<p>Bug Fix(es) and Enhancement(s):</p>
<p>*…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rlsa-2026:90365"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64523</id>
    <title>UBUNTU-CVE-2026-64523</title>
    <updated>2026-11-21T15:12:24.223428+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 154 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: net/handshake: Take a long-lived file reference at submit handshake_nl_accept_doit() needs the file pointer backing req-&gt;hr_sk-&gt;sk_socket to survive the window between handshake_req_next() and the subsequent FD_PREPARE() and get_file(). The submit-side sock_hold() does not provide that.  sk_refcnt keeps struct sock alive, but struct socket is owned by sock-&gt;file: when the consumer fputs the last file reference, sock_release() tears the socket down regardless of any sock_hold. Add an hr_file pointer to struct handshake_req and acquire an explicit reference on sock-&gt;file during handshake_req_submit(). handshake_complete() and handshake_req_cancel() release the reference on the completion-bit-winning path. The submit error path must also release the file reference, but after rhashtable insertion a concurrent handshake_req_cancel() can discover the request and race the error path.  Gate the error-path cleanup -- sk_destruct restoration, fput, and request destruction -- with test_and_set_bit(HANDSHAKE_F_REQ_COMPLETED), the same serialization handshake_complete() and handshake_req_cancel() already use.  When cancel has already claimed ownership, the submit error path returns without touching the request; socket teardown handles final destruction. The accept-side dereferences are not yet retargeted; that change comes in the next patch.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64523"/>
  </entry>
</feed>
