<?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-19T19:41:51.064905+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-2024-40910</id>
    <title>BELL-CVE-2024-40910</title>
    <updated>2026-11-19T19:41:51.082764+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-2024-40910"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2024-avi-0613</id>
    <title>certfr-2024-avi-0613 — 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-19T19:41:51.082841+00:00</updated>
    <content>certfr-2024-avi-0613</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2024-avi-0613"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2024-1961</id>
    <title>OESA-2024-1961 — kernel security update</title>
    <updated>2026-11-19T19:41:51.082862+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):

In the Linux kernel, the following vulnerability has been resolved:

NFSD: Fix the behavior of READ near OFFSET_MAX

Dan Aloni reports:
&amp;gt; Due to commit 8cfb9015280d (&amp;quot;NFS: Always provide aligned buffers to
&amp;gt; the RPC read layers&amp;quot;) on the client, a read of 0xfff is aligned up
&amp;gt; to server rsize of 0x1000.
&amp;gt;
&amp;gt; As a result, in a test where the server has a file of size
&amp;gt; 0x7fffffffffffffff, and the client tries to read from the offset
&amp;gt; 0x7ffffffffffff000, the read causes loff_t overflow in the server
&amp;gt; and it returns an NFS code of EINVAL to the client. The client as
&amp;gt; a result indefinitely retries the request.

The Linux NFS client does not handle NFS?ERR_INVAL, even though all
NFS specifications permit servers to return that status code for a
READ.

Instead of NFS?ERR_INVAL, have out-of-range READ requests succeed
and return a short result. Set the EOF flag in the result to prevent
the client from retrying the READ request. This behavior appears to
be consistent with Solaris NFS servers.

Note that NFSv3 and NFSv4 use u64 offset values on the wire. These
must be converted to loff_t internally before use -- an implicit
type cast is not adequate for this purpose. Otherwise VFS checks
against sb-&amp;gt;s_maxbytes do not work properly.(CVE-2022-48827)

In the Linux kernel, the following vulnerability has been resolved:

net: can: j1939: enhanced error handlin…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2024-1961"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40910</id>
    <title>UBUNTU-CVE-2024-40910</title>
    <updated>2026-11-19T19:41:51.083131+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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, Ubuntu:Pro:16.04:LTS: linux-kvm and 174 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: ax25: Fix refcount imbalance on inbound connections When releasing a socket in ax25_release(), we call netdev_put() to decrease the refcount on the associated ax.25 device. However, the execution path for accepting an incoming connection never calls netdev_hold(). This imbalance leads to refcount errors, and ultimately to kernel crashes. A typical call trace for the above situation will start with one of the following errors:     refcount_t: decrement hit 0; leaking memory.     refcount_t: underflow; use-after-free. And will then have a trace like:     Call Trace:     &lt;TASK&gt;     ? show_regs+0x64/0x70     ? __warn+0x83/0x120     ? refcount_warn_saturate+0xb2/0x100     ? report_bug+0x158/0x190     ? prb_read_valid+0x20/0x30     ? handle_bug+0x3e/0x70     ? exc_invalid_op+0x1c/0x70     ? asm_exc_invalid_op+0x1f/0x30     ? refcount_warn_saturate+0xb2/0x100     ? refcount_warn_saturate+0xb2/0x100     ax25_release+0x2ad/0x360     __sock_release+0x35/0xa0     sock_close+0x19/0x20     [...] On reboot (or any attempt to remove the interface), the kernel gets stuck in an infinite loop:     unregister_netdevice: waiting for ax0 to become free. Usage count = 0 This patch corrects these issues by ensuring that we call netdev_hold() and ax25_dev_hold() for new connections in ax25_accept(). This makes the logic leading to ax25_accept() match the logic for ax25_bind(): in both cases we increment the refcount, which is ultim…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40910"/>
  </entry>
</feed>
