<?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-02T20:31:50.297710+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:2026-02190</id>
    <title>bdu:2026-02190</title>
    <updated>2026-10-02T20:31:50.938559+00:00</updated>
    <content>bdu:2026-02190</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-02190"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2023-53282</id>
    <title>BELL-CVE-2023-53282</title>
    <updated>2026-10-02T20:31:50.938619+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2023-53282"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895</id>
    <title>certfr-2025-avi-0895 — 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-02T20:31:50.938650+00:00</updated>
    <content>certfr-2025-avi-0895</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-311950</id>
    <title>EUVD-2026-311950</title>
    <updated>2026-10-02T20:31:50.938669+00:00</updated>
    <content>EUVD-2026-311950</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-311950"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53282</id>
    <title>fkie_cve-2023-53282</title>
    <updated>2026-10-02T20:31:50.938681+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>scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write</p>
<p>During the sysfs firmware write process, a use-after-free read warning is
logged from the lpfc_wr_object() routine:</p>
<p>BUG: KFENCE: use-after-free read in lpfc_wr_object+0x235/0x310 [lpfc]
  Use-after-free read at 0x0000000000cf164d (in kfence-#111):
  lpfc_wr_object+0x235/0x310 [lpfc]
  lpfc_write_firmware.cold+0x206/0x30d [lpfc]
  lpfc_sli4_request_firmware_update+0xa6/0x100 [lpfc]
  lpfc_request_firmware_upgrade_store+0x66/0xb0 [lpfc]
  kernfs_fop_write_iter+0x121/0x1b0
  new_sync_write+0x11c/0x1b0
  vfs_write+0x1ef/0x280
  ksys_write+0x5f/0xe0
  do_syscall_64+0x59/0x90
  entry_SYSCALL_64_after_hwframe+0x63/0xcd</p>
<p>The driver accessed wr_object pointer data, which was initialized into
mailbox payload memory, after the mailbox object was released back to the
mailbox pool.</p>
<p>Fix by moving the mailbox free calls to the end of the routine ensuring
that we don't reference internal mailbox memory after release.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-53282"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-7wcq-h796-g66p</id>
    <title>GHSA-7wcq-h796-g66p</title>
    <updated>2026-10-02T20:31:50.938719+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>scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write</p>
<p>During the sysfs firmware write process, a use-after-free read warning is
logged from the lpfc_wr_object() routine:</p>
<p>BUG: KFENCE: use-after-free read in lpfc_wr_object+0x235/0x310 [lpfc]
  Use-after-free read at 0x0000000000cf164d (in kfence-#111):
  lpfc_wr_object+0x235/0x310 [lpfc]
  lpfc_write_firmware.cold+0x206/0x30d [lpfc]
  lpfc_sli4_request_firmware_update+0xa6/0x100 [lpfc]
  lpfc_request_firmware_upgrade_store+0x66/0xb0 [lpfc]
  kernfs_fop_write_iter+0x121/0x1b0
  new_sync_write+0x11c/0x1b0
  vfs_write+0x1ef/0x280
  ksys_write+0x5f/0xe0
  do_syscall_64+0x59/0x90
  entry_SYSCALL_64_after_hwframe+0x63/0xcd</p>
<p>The driver accessed wr_object pointer data, which was initialized into
mailbox payload memory, after the mailbox object was released back to the
mailbox pool.</p>
<p>Fix by moving the mailbox free calls to the end of the routine ensuring
that we don't reference internal mailbox memory after release.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-7wcq-h796-g66p"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2025-2800</id>
    <title>OESA-2025-2800 — kernel security update</title>
    <updated>2026-10-02T20:31:50.938744+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):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ext4: update s_journal_inum if it changes after journal replay</p>
<p>When mounting a crafted ext4 image, s_journal_inum may change after journal
replay, which is obviously unreasonable because we have successfully loaded
and replayed the journal through the old s_journal_inum. And the new
s_journal_inum bypasses some of the checks in ext4_get_journal(), which
may trigger a null pointer dereference problem. So if s_journal_inum
changes after the journal replay, we ignore the change, and rewrite the
current journal_inum to the superblock.(CVE-2023-53091)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>vxlan: Fix nexthop hash size</p>
<p>The nexthop code expects a 31 bit hash, such as what is returned by
fib_multipath_hash() and rt6_multipath_hash(). Passing the 32 bit hash
returned by skb_get_hash() can lead to problems related to the fact that
&amp;apos;int hash&amp;apos; is a negative number when the MSB is set.</p>
<p>In the case of hash threshold nexthop groups, nexthop_select_path_hthr()
will disproportionately select the first nexthop group entry. In the case
of resilient nexthop groups, nexthop_select_path_res() may do an out of
bounds access in nh_buckets[], for example:
    hash = -912054133
    num_nh_buckets = 2
    bucket_index = 65535</p>
<p>which leads to the following panic:</p>
<p>BUG: unable to handle page fault for address: ffffc9000…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2025-2800"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2025:03615-1</id>
    <title>SUSE-SU-2025:03615-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-02T20:31:50.939019+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-2025:03615-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53282</id>
    <title>UBUNTU-CVE-2023-53282</title>
    <updated>2026-10-02T20:31:50.939294+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 159 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write During the sysfs firmware write process, a use-after-free read warning is logged from the lpfc_wr_object() routine:   BUG: KFENCE: use-after-free read in lpfc_wr_object+0x235/0x310 [lpfc]   Use-after-free read at 0x0000000000cf164d (in kfence-#111):   lpfc_wr_object+0x235/0x310 [lpfc]   lpfc_write_firmware.cold+0x206/0x30d [lpfc]   lpfc_sli4_request_firmware_update+0xa6/0x100 [lpfc]   lpfc_request_firmware_upgrade_store+0x66/0xb0 [lpfc]   kernfs_fop_write_iter+0x121/0x1b0   new_sync_write+0x11c/0x1b0   vfs_write+0x1ef/0x280   ksys_write+0x5f/0xe0   do_syscall_64+0x59/0x90   entry_SYSCALL_64_after_hwframe+0x63/0xcd The driver accessed wr_object pointer data, which was initialized into mailbox payload memory, after the mailbox object was released back to the mailbox pool. Fix by moving the mailbox free calls to the end of the routine ensuring that we don't reference internal mailbox memory after release.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53282"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2053</id>
    <title>WID-SEC-W-2025-2053 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-02T20:31:50.939510+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2053"/>
  </entry>
</feed>
