<?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-21T02:36:38.825980+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-2024:8617</id>
    <title>ALSA-2024:8617 — Moderate: kernel security update</title>
    <updated>2026-11-21T02:36:38.843245+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:9: bpftool, 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 and 52 more</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>* hw: cpu: intel: Native Branch History Injection (BHI) (CVE-2024-2201)
  * kernel: tcp: add sanity checks to rx zerocopy (CVE-2024-26640)
  * kernel: mptcp: fix data re-injection from stale subflow (CVE-2024-26826)
  * kernel: af_unix: Fix garbage collector racing against connect() (CVE-2024-26923)
  * kernel: mac802154: fix llsec key resources release in mac802154_llsec_key_del (CVE-2024-26961)
  * kernel: scsi: core: Fix unremoved procfs host directory regression (CVE-2024-26935)
  * kernel: tty: Fix out-of-bound vmalloc access in imageblit (CVE-2021-47383)
  * kernel: net/sched: taprio: extend minimum interval restriction to entire cycle too (CVE-2024-36244)
  * kernel: xfs: fix log recovery buffer allocation for the legacy h_size fixup (CVE-2024-39472)
  * kernel: netfilter: nft_inner: validate mandatory meta and payload (CVE-2024-39504)
  * kernel: USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages (CVE-2024-40904)
  * kernel: mptcp: ensure snd_una is properly initialized on connect (CVE-2024-40931)
  * kernel: ipv6: prevent possible NULL dereference in rt6_probe() (CVE-2024-40960)
  * kernel: ext4: do not create EA inode under buffer lock (CVE-2024-40972)
  * kernel: wifi: mt76: mt7921s: fix potential hung tasks during chip recovery (CVE-2024-40977)
  * kernel: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() (CVE-202…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2024:8617"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2024-26935</id>
    <title>BELL-CVE-2024-26935</title>
    <updated>2026-11-21T02:36:38.843410+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-26935"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2024-avi-0381</id>
    <title>certfr-2024-avi-0381 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
    <updated>2026-11-21T02:36:38.843436+00:00</updated>
    <content>certfr-2024-avi-0381</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2024-avi-0381"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2024-1738</id>
    <title>OESA-2024-1738 — kernel security update</title>
    <updated>2026-11-21T02:36:38.843452+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP3: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):

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

afs: Fix corruption in reads at fpos 2G-4G from an OpenAFS server

AFS-3 has two data fetch RPC variants, FS.FetchData and FS.FetchData64, and
Linux&amp;apos;s afs client switches between them when talking to a non-YFS server
if the read size, the file position or the sum of the two have the upper 32
bits set of the 64-bit value.

This is a problem, however, since the file position and length fields of
FS.FetchData are *signed* 32-bit values.

Fix this by capturing the capability bits obtained from the fileserver when
it&amp;apos;s sent an FS.GetCapabilities RPC, rather than just discarding them, and
then picking out the VICED_CAPABILITY_64BITFILES flag.  This can then be
used to decide whether to use FS.FetchData or FS.FetchData64 - and also
FS.StoreData or FS.StoreData64 - rather than using upper_32_bits() to
switch on the parameter values.

This capabilities flag could also be used to limit the maximum size of the
file, but all servers must be checked for that.

Note that the issue does not exist with FS.StoreData - that uses *unsigned*
32-bit values.  It&amp;apos;s also not a problem with Auristor servers as its
YFS.FetchData64 op uses unsigned 64-bit values.

This can be tested by cloning a git repo through an OpenAFS client to an
OpenAFS server and then doing &amp;quot;git status&amp;quot; on it from a Linux afs
client[1].  Provided…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2024-1738"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26935</id>
    <title>UBUNTU-CVE-2024-26935</title>
    <updated>2026-11-21T02:36:38.843775+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 138 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix unremoved procfs host directory regression Commit fc663711b944 ("scsi: core: Remove the /proc/scsi/${proc_name} directory earlier") fixed a bug related to modules loading/unloading, by adding a call to scsi_proc_hostdir_rm() on scsi_remove_host(). But that led to a potential duplicate call to the hostdir_rm() routine, since it's also called from scsi_host_dev_release(). That triggered a regression report, which was then fixed by commit be03df3d4bfe ("scsi: core: Fix a procfs host directory removal regression"). The fix just dropped the hostdir_rm() call from dev_release(). But it happens that this proc directory is created on scsi_host_alloc(), and that function "pairs" with scsi_host_dev_release(), while scsi_remove_host() pairs with scsi_add_host(). In other words, it seems the reason for removing the proc directory on dev_release() was meant to cover cases in which a SCSI host structure was allocated, but the call to scsi_add_host() didn't happen. And that pattern happens to exist in some error paths, for example. Syzkaller causes that by using USB raw gadget device, error'ing on usb-storage driver, at usb_stor_probe2(). By checking that path, we can see that the BadDevice label leads to a scsi_host_put() after a SCSI host allocation, but there's no call to scsi_add_host() in such path. That leads to messages like this in dmesg (and a leak of the SCSI host proc structure): usb-storage 4-1:…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26935"/>
  </entry>
</feed>
