<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T09:02:35.311908+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/bdu:2025-03413</id>
    <title>bdu:2025-03413</title>
    <updated>2026-10-03T09:02:36.114300+00:00</updated>
    <content>bdu:2025-03413</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-03413"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2024-47672</id>
    <title>BELL-CVE-2024-47672</title>
    <updated>2026-10-03T09:02:36.114366+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://cve.radiocsirt.org/vuln/bell-cve-2024-47672"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0999</id>
    <title>certfr-2024-avi-0999 — 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-10-03T09:02:36.114400+00:00</updated>
    <content>certfr-2024-avi-0999</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2024-avi-0999"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-47672</id>
    <title>fkie_cve-2024-47672</title>
    <updated>2026-10-03T09:02:36.114419+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-47672"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-8p54-hh75-4mh9</id>
    <title>GHSA-8p54-hh75-4mh9</title>
    <updated>2026-10-03T09:02:36.114445+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>wifi: iwlwifi: mvm: don't wait for tx queues if firmware is dead</p>
<p>There is a WARNING in iwl_trans_wait_tx_queues_empty() (that was
recently converted from just a message), that can be hit if we
wait for TX queues to become empty after firmware died. Clearly,
we can't expect anything from the firmware after it's declared dead.</p>
<p>Don't call iwl_trans_wait_tx_queues_empty() in this case. While it could
be a good idea to stop the flow earlier, the flush functions do some
maintenance work that is not related to the firmware, so keep that part
of the code running even when the firmware is not running.</p>
<p>[edit commit message]</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-8p54-hh75-4mh9"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2024-47672</id>
    <title>msrc_CVE-2024-47672 — wifi: iwlwifi: mvm: don't wait for tx queues if firmware is dead</title>
    <updated>2026-10-03T09:02:36.114469+00:00</updated>
    <content>msrc_CVE-2024-47672</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2024-47672"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2024-2255</id>
    <title>OESA-2024-2255 — kernel security update</title>
    <updated>2026-10-03T09:02:36.114487+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://cve.radiocsirt.org/vuln/oesa-2024-2255"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2024:3983-1</id>
    <title>SUSE-SU-2024:3983-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-03T09:02:36.114676+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2024:3983-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47672</id>
    <title>UBUNTU-CVE-2024-47672</title>
    <updated>2026-10-03T09:02:36.114807+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: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 and 156 more</p>
<p>Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47672"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3134</id>
    <title>WID-SEC-W-2024-3134 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-03T09:02:36.115013+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen oder um einen unspezifischen Angriff durchzuführen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3134"/>
  </entry>
</feed>
