<?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-21T11:43:46.751271+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:7000</id>
    <title>ALSA-2024:7000 — Important: kernel security update</title>
    <updated>2026-11-21T11:43:46.771094+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 more</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.  
Security Fix(es):</p>
<p>CVE-2023-6040  CVE-2024-26595  CVE-2024-26600  CVE-2021-46984  CVE-2023-52478  CVE-2023-52476  CVE-2023-52522  CVE-2021-47101  CVE-2021-47097  CVE-2023-52605  CVE-2024-26638  CVE-2024-26645  CVE-2024-26665  CVE-2024-26720  CVE-2024-26717  CVE-2024-26769  CVE-2024-26846  CVE-2024-26894  CVE-2024-26880  CVE-2024-26855  CVE-2024-26923  CVE-2024-26939  CVE-2024-27013  CVE-2024-27042  CVE-2024-35809  CVE-2023-52683  CVE-2024-35884  CVE-2024-35877  CVE-2024-35944  CVE-2024-35989  CVE-2021-47412  CVE-2021-47393  CVE-2021-47386  CVE-2021-47385  CVE-2021-47384  CVE-2021-47383  CVE-2021-47432  CVE-2021-47352  CVE-2021-47338  CVE-2021-47321  CVE-2021-47289  CVE-2021-47287  CVE-2023-52798  CVE-2023-52809  CVE-2023-52817  CVE-2023-52840  CVE-2023-52800  CVE-2021-47441  CVE-2021-47466  CVE-2021-47455  CVE-2021-47497  CVE-2021-47560  CVE-2021-47527  CVE-2024-36883  CVE-2024-36922  CVE-2024-36920  CVE-2024-36902  CVE-2024-36953  CVE-2024-36939  CVE-2024-36919  CVE-2024-36901  CVE-2021-47582  CVE-2021-47609  CVE-2024-38619  CVE-2022-48754  CVE-2022-48760  CVE-2024-38581  CVE-2024-38579  CVE-2024-38570  CVE-2024-38559  CVE-2024-38558  CVE-2024-37356  CVE-2024-39471  CVE-2024-39499  CVE-2024-39501  CVE-2024-39506  CVE-2024-40904  CVE-2024-40911  CVE-2024-40912  CVE-2024-40929  CVE-2024-40931  CVE-2024-40941  CVE-2024-40954  CVE-2024-40958  CVE-2024-40959  CVE-2024-40960  CVE-2024-40972…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2024:7000"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2024-40998</id>
    <title>BELL-CVE-2024-40998</title>
    <updated>2026-11-21T11:43:46.771212+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-40998"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2024-avi-0669</id>
    <title>certfr-2024-avi-0669 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-11-21T11:43:46.771236+00:00</updated>
    <content>certfr-2024-avi-0669</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2024-avi-0669"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2024-2255</id>
    <title>OESA-2024-2255 — kernel security update</title>
    <updated>2026-11-21T11:43:46.771272+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:

drm/i915/gt: Cleanup partial engine discovery failures

If we abort driver initialisation in the middle of gt/engine discovery,
some engines will be fully setup and some not. Those incompletely setup
engines only have &amp;apos;engine-&amp;gt;release == NULL&amp;apos; and so will leak any of the
common objects allocated.

v2:
 - Drop the destroy_pinned_context() helper for now.  It&amp;apos;s not really
   worth it with just a single callsite at the moment.  (Janusz)(CVE-2022-48893)

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

f2fs: fix to avoid dirent corruption

As Al reported in link[1]:

f2fs_rename()
...
	if (old_dir != new_dir &amp;amp;&amp;amp; !whiteout)
		f2fs_set_link(old_inode, old_dir_entry,
					old_dir_page, new_dir);
	else
		f2fs_put_page(old_dir_page, 0);

You want correct inumber in the &amp;quot;..&amp;quot; link.  And cross-directory
rename does move the source to new parent, even if you&amp;apos;d been asked
to leave a whiteout in the old place.

[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/

With below testcase, it may cause dirent corruption, due to it missed
to call f2fs_set_link() to update &amp;quot;..&amp;quot; link to new directory.
- mkdir -p dir/foo
- renameat2 -w dir/foo bar

[ASSERT] (__chk_dots_dentries:1421)  --&amp;gt; Bad inode number[0x4] for &amp;apos;..&amp;apos;, parent parent ino is [0…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2024-2255"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40998</id>
    <title>UBUNTU-CVE-2024-40998</title>
    <updated>2026-11-21T11:43:46.771465+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 187 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: ext4: fix uninitialized ratelimit_state-&gt;lock access in __ext4_fill_super() In the following concurrency we will access the uninitialized rs-&gt;lock: ext4_fill_super   ext4_register_sysfs    // sysfs registered msg_ratelimit_interval_ms                              // Other processes modify rs-&gt;interval to                              // non-zero via msg_ratelimit_interval_ms   ext4_orphan_cleanup     ext4_msg(sb, KERN_INFO, "Errors on filesystem, "       __ext4_msg         ___ratelimit(&amp;(EXT4_SB(sb)-&gt;s_msg_ratelimit_state)           if (!rs-&gt;interval)  // do nothing if interval is 0             return 1;           raw_spin_trylock_irqsave(&amp;rs-&gt;lock, flags)             raw_spin_trylock(lock)               _raw_spin_trylock                 __raw_spin_trylock                   spin_acquire(&amp;lock-&gt;dep_map, 0, 1, _RET_IP_)                     lock_acquire                       __lock_acquire                         register_lock_class                           assign_lock_key                             dump_stack();   ratelimit_state_init(&amp;sbi-&gt;s_msg_ratelimit_state, 5 * HZ, 10);     raw_spin_lock_init(&amp;rs-&gt;lock);     // init rs-&gt;lock here and get the following dump_stack: ========================================================= INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe you didn't initialize this object before use? turning off the locking correctness validat…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40998"/>
  </entry>
</feed>
