<?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-21T04:07:43.856010+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-42106</id>
    <title>BELL-CVE-2024-42106</title>
    <updated>2026-11-21T04:07:43.865305+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-42106"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2024-avi-0719</id>
    <title>certfr-2024-avi-0719 — 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-21T04:07:43.865359+00:00</updated>
    <content>certfr-2024-avi-0719</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2024-avi-0719"/>
  </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-21T04:07:43.865382+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-42106</id>
    <title>UBUNTU-CVE-2024-42106</title>
    <updated>2026-11-21T04:07:43.865578+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, 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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 179 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: inet_diag: Initialize pad field in struct inet_diag_req_v2 KMSAN reported uninit-value access in raw_lookup() [1]. Diag for raw sockets uses the pad field in struct inet_diag_req_v2 for the underlying protocol. This field corresponds to the sdiag_raw_protocol field in struct inet_diag_req_raw. inet_diag_get_exact_compat() converts inet_diag_req to inet_diag_req_v2, but leaves the pad field uninitialized. So the issue occurs when raw_lookup() accesses the sdiag_raw_protocol field. Fix this by initializing the pad field in inet_diag_get_exact_compat(). Also, do the same fix in inet_diag_dump_compat() to avoid the similar issue in the future. [1] BUG: KMSAN: uninit-value in raw_lookup net/ipv4/raw_diag.c:49 [inline] BUG: KMSAN: uninit-value in raw_sock_get+0x657/0x800 net/ipv4/raw_diag.c:71  raw_lookup net/ipv4/raw_diag.c:49 [inline]  raw_sock_get+0x657/0x800 net/ipv4/raw_diag.c:71  raw_diag_dump_one+0xa1/0x660 net/ipv4/raw_diag.c:99  inet_diag_cmd_exact+0x7d9/0x980  inet_diag_get_exact_compat net/ipv4/inet_diag.c:1404 [inline]  inet_diag_rcv_msg_compat+0x469/0x530 net/ipv4/inet_diag.c:1426  sock_diag_rcv_msg+0x23d/0x740 net/core/sock_diag.c:282  netlink_rcv_skb+0x537/0x670 net/netlink/af_netlink.c:2564  sock_diag_rcv+0x35/0x40 net/core/sock_diag.c:297  netlink_unicast_kernel net/netlink/af_netlink.c:1335 [inline]  netlink_unicast+0xe74/0x1240 net/netlink/af_netlink.c:1361  netlink_sendmsg+0x10c6/0x1260 net/net…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2024-42106"/>
  </entry>
</feed>
