<?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-19T17:57:58.552793+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-42290</id>
    <title>BELL-CVE-2024-42290</title>
    <updated>2026-11-19T17:57:58.566041+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-42290"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2024-avi-0779</id>
    <title>certfr-2024-avi-0779 — 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-19T17:57:58.566104+00:00</updated>
    <content>certfr-2024-avi-0779</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2024-avi-0779"/>
  </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-19T17:57:58.566124+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-42290</id>
    <title>UBUNTU-CVE-2024-42290</title>
    <updated>2026-11-19T17:57:58.566353+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 159 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: irqchip/imx-irqsteer: Handle runtime power management correctly The power domain is automatically activated from clk_prepare(). However, on certain platforms like i.MX8QM and i.MX8QXP, the power-on handling invokes sleeping functions, which triggers the 'scheduling while atomic' bug in the context switch path during device probing:  BUG: scheduling while atomic: kworker/u13:1/48/0x00000002  Call trace:   __schedule_bug+0x54/0x6c   __schedule+0x7f0/0xa94   schedule+0x5c/0xc4   schedule_preempt_disabled+0x24/0x40   __mutex_lock.constprop.0+0x2c0/0x540   __mutex_lock_slowpath+0x14/0x20   mutex_lock+0x48/0x54   clk_prepare_lock+0x44/0xa0   clk_prepare+0x20/0x44   imx_irqsteer_resume+0x28/0xe0   pm_generic_runtime_resume+0x2c/0x44   __genpd_runtime_resume+0x30/0x80   genpd_runtime_resume+0xc8/0x2c0   __rpm_callback+0x48/0x1d8   rpm_callback+0x6c/0x78   rpm_resume+0x490/0x6b4   __pm_runtime_resume+0x50/0x94   irq_chip_pm_get+0x2c/0xa0   __irq_do_set_handler+0x178/0x24c   irq_set_chained_handler_and_data+0x60/0xa4   mxc_gpio_probe+0x160/0x4b0 Cure this by implementing the irq_bus_lock/sync_unlock() interrupt chip callbacks and handle power management in them as they are invoked from non-atomic context. [ tglx: Rewrote change log, added Fixes tag ]</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2024-42290"/>
  </entry>
</feed>
