<?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-20T23:34:53.106240+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:93413</id>
    <title>ALSA-2026:93413 — Important: kernel security, bug fix, and enhancement update</title>
    <updated>2026-11-20T23:34:53.119585+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>* kernel: Kernel: Denial of Service in network socket error handling (CVE-2026-22977)
  * kernel: x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache (CVE-2026-46174)
  * kernel: i2c: stub: Reject I2C block transfers with invalid length (CVE-2026-64191)
  * kernel: Linux kernel: PPP over L2TP Use-After-Free vulnerability (CVE-2026-68398)
  * kernel: mptcp: pm: userspace: fix use-after-free in get_local_id (CVE-2026-68169)
  * kernel: tipc: require net admin for TIPCv2 netlink mutators (CVE-2026-74283)
  * kernel: mptcp: options: reset DSS fields in case of unexpected size (CVE-2026-80586)
  * kernel: entry: Fix seccomp bypass after ptrace with TSYNC (CVE-2026-89603)
  * kernel: KVM: nVMX: Always flush vpid02 on first use (CVE-2026-89932)
  * kernel: scsi: target: iscsi: Reserve a terminator byte for the login payload (CVE-2026-90011)
  * kernel: virtio-fs: avoid double-free on failed queue setup (CVE-2026-93827)
  * kernel: smb: client: bound dirent name against end of SMB response in cifs_filldir (CVE-2026-93787)
  * kernel: KEYS: encrypted: fix integer overflow of datablob_len (CVE-2026-98222)
  * kernel: xfrm: hold net_device reference under RCU in bundle creation (CVE-2026-98364)
  * kernel: ipv4: free inet_opt and ireq_opt after an RCU grace period (CVE-2026-98432)
  * kernel: nvmet-auth: fix out-of-bounds write in nvmet_auth_challen…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2026:93413"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-22977</id>
    <title>BELL-CVE-2026-22977</title>
    <updated>2026-11-20T23:34:53.119663+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-22977"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0166</id>
    <title>certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
    <updated>2026-11-20T23:34:53.119678+00:00</updated>
    <content>certfr-2026-avi-0166</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0166"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-1566</id>
    <title>OESA-2026-1566 — kernel security update</title>
    <updated>2026-11-20T23:34:53.119686+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>udp: Deal with race between UDP socket address change and rehash</p>
<p>If a UDP socket changes its local address while it&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.</p>
<p>Secondary hash chains were introduced by commit 30fff9231fad (&amp;quot;udp:
bind() optimisation&amp;quot;) and, as a result, a rehash operation became
needed to make a bound socket reachable again after a connect().</p>
<p>This operation was introduced by commit 719f835853a9 (&amp;quot;udp: add
rehash on connect()&amp;quot;) which isn&amp;apos;t however a complete fix: the
socket will be found once the rehashing completes, but not while
it&amp;apos;s pending.</p>
<p>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.</p>
<p>Now, if the client, running on a different CPU thread, happens to
send a (subsequent) datagram while the server&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…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-1566"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rlsa-2026:93413</id>
    <title>RLSA-2026:93413 — Important: kernel security, bug fix, and enhancement update</title>
    <updated>2026-11-20T23:34:53.119925+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:10: kernel, Rocky Linux:10: kernel-tools-debuginfo, Rocky Linux:10: kernel-64k-modules, Rocky Linux:10: kernel-debug-modules-extra, Rocky Linux:10: kernel-64k-debug-devel-matched, Rocky Linux:10: kernel-rt, Rocky Linux:10: kernel-rt-64k-modules, Rocky Linux:10: kernel-64k, Rocky Linux:10: kernel-64k-devel-matched, Rocky Linux:10: kernel-rt-64k-debug and 80 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: Kernel: Denial of Service in network socket error handling (CVE-2026-22977)</p>
<p>* kernel: x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache (CVE-2026-46174)</p>
<p>* kernel: i2c: stub: Reject I2C block transfers with invalid length (CVE-2026-64191)</p>
<p>* kernel: Linux kernel: PPP over L2TP Use-After-Free vulnerability (CVE-2026-68398)</p>
<p>* kernel: mptcp: pm: userspace: fix use-after-free in get_local_id (CVE-2026-68169)</p>
<p>* kernel: tipc: require net admin for TIPCv2 netlink mutators (CVE-2026-74283)</p>
<p>* kernel: mptcp: options: reset DSS fields in case of unexpected size (CVE-2026-80586)</p>
<p>* kernel: entry: Fix seccomp bypass after ptrace with TSYNC (CVE-2026-89603)</p>
<p>* kernel: KVM: nVMX: Always flush vpid02 on first use (CVE-2026-89932)</p>
<p>* kernel: scsi: target: iscsi: Reserve a terminator byte for the login payload (CVE-2026-90011)</p>
<p>* kernel: virtio-fs: avoid double-free on failed queue setup (CVE-2026-93827)</p>
<p>* kernel: smb: client: bound dirent name against end of SMB response in cifs_filldir (CVE-2026-93787)</p>
<p>* kernel: KEYS: encrypted: fix integer overflow of datablob_len (CVE-2026-98222)</p>
<p>* kernel: xfrm: hold net_device reference under RCU in bundle creation (CVE-2026-98364)</p>
<p>* kernel: ipv4: free inet_opt and ireq_opt after an RCU grace period (CVE-2026-98432)</p>
<p>* kernel: nvmet-auth: fix out-of-bounds write in nvmet_auth_challenge() (CVE-2026-98725)…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rlsa-2026:93413"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-22977</id>
    <title>UBUNTU-CVE-2026-22977</title>
    <updated>2026-11-20T23:34:53.120000+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: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 204 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: net: sock: fix hardened usercopy panic in sock_recv_errqueue skbuff_fclone_cache was created without defining a usercopy region, [1] unlike skbuff_head_cache which properly whitelists the cb[] field. [2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is enabled and the kernel attempts to copy sk_buff.cb data to userspace via sock_recv_errqueue() -&gt; put_cmsg(). The crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone()    (from skbuff_fclone_cache) [1] 2. The skb is cloned via skb_clone() using the pre-allocated fclone [3] 3. The cloned skb is queued to sk_error_queue for timestamp reporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE) 5. sock_recv_errqueue() calls put_cmsg() to copy serr-&gt;ee from skb-&gt;cb [4] 6. __check_heap_object() fails because skbuff_fclone_cache has no    usercopy whitelist [5] When cloned skbs allocated from skbuff_fclone_cache are used in the socket error queue, accessing the sock_exterr_skb structure in skb-&gt;cb via put_cmsg() triggers a usercopy hardening violation: [    5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object 'skbuff_fclone_cache' (offset 296, size 16)! [    5.382796] kernel BUG at mm/usercopy.c:102! [    5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI [    5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7 [    5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-22977"/>
  </entry>
</feed>
