<?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-21T06:03:53.342580+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/bell-cve-2026-64436</id>
    <title>BELL-CVE-2026-64436</title>
    <updated>2026-11-21T06:03:53.366833+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-64436"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0982</id>
    <title>certfr-2026-avi-0982 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
    <updated>2026-11-21T06:03:53.366892+00:00</updated>
    <content>certfr-2026-avi-0982</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0982"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-3532</id>
    <title>OESA-2026-3532 — kernel security update</title>
    <updated>2026-11-21T06:03:53.366912+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: 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>uaccess: fix integer overflow on access_ok()</p>
<p>Three architectures check the end of a user access against the
address limit without taking a possible overflow into account.
Passing a negative length or another overflow in here returns
success when it should not.</p>
<p>Use the most common correct implementation here, which optimizes
for a constant &amp;apos;size&amp;apos; argument, and turns the common case into a
single comparison.(CVE-2022-49289)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>parisc: Fix double SIGFPE crash</p>
<p>Camm noticed that on parisc a SIGFPE exception will crash an application with
a second SIGFPE in the signal handler.  Dave analyzed it, and it happens
because glibc uses a double-word floating-point store to atomically update
function descriptors. As a result of lazy binding, we hit a floating-point
store in fpe_func almost immediately.</p>
<p>When the T bit is set, an assist exception trap occurs when when the
co-processor encounters *any* floating-point instruction except for a double
store of register %fr0.  The latter cancels all pending traps.  Let&amp;apos;s fix this
by clearing the Trap (T) bit in the FP status register before returning to the
signal handler in userspace.</p>
<p>The issue can be reproduced with this test program:</p>
<p>root@parisc:~# cat fpe.c</p>
<p>static void fpe_func(int sig, siginfo_t *i, void *v) {…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-3532"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64436</id>
    <title>UBUNTU-CVE-2026-64436</title>
    <updated>2026-11-21T06:03:53.367126+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 248 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: net: af_key: initialize alg_key_len for IPComp states pfkey_msg2xfrm_state() handles the IPComp (SADB_X_SATYPE_IPCOMP) case by allocating x-&gt;calg and copying only the algorithm name: 	x-&gt;calg = kmalloc_obj(*x-&gt;calg); 	if (!x-&gt;calg) { 		err = -ENOMEM; 		goto out; 	} 	strcpy(x-&gt;calg-&gt;alg_name, a-&gt;name); 	x-&gt;props.calgo = sa-&gt;sadb_sa_encrypt; Unlike the authentication (x-&gt;aalg) and encryption (x-&gt;ealg) branches of the same function, the compression branch never initializes calg-&gt;alg_key_len.  IPComp carries no key and the allocation only reserves sizeof(struct xfrm_algo) (i.e. no room for a key), so the field is left containing uninitialized slab data. calg-&gt;alg_key_len is later used as a length by xfrm_algo_clone() when an IPComp state is cloned during XFRM_MSG_MIGRATE: 	xfrm_state_migrate() 	  xfrm_state_clone_and_setup() 	    x-&gt;calg = xfrm_algo_clone(orig-&gt;calg); 	      kmemdup(orig, xfrm_alg_len(orig)); where xfrm_alg_len() returns sizeof(*alg) + (alg_key_len + 7) / 8.  With a non-zero garbage alg_key_len, kmemdup() reads past the end of the 68-byte calg object.  Adding an IPComp SA via PF_KEY and then migrating it triggers (net-next, KASAN, init_on_alloc=0):   BUG: KASAN: slab-out-of-bounds in kmemdup_noprof+0x44/0x60   Read of size 4164 at addr ff11000025a74980 by task diag2/9287   CPU: 3 UID: 0 PID: 9287 Comm: diag2 7.1.0-rc6-g903db046d557 #1   Call Trace:    &lt;TASK&gt;    dump_stack_lvl+0x10e/0x1f0    prin…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64436"/>
  </entry>
</feed>
