<?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-05T03:10:20.187498+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-01932</id>
    <title>bdu:2025-01932</title>
    <updated>2026-10-05T03:10:20.529047+00:00</updated>
    <content>bdu:2025-01932</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-01932"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2024-43875</id>
    <title>BELL-CVE-2024-43875</title>
    <updated>2026-10-05T03:10:20.529111+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-43875"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/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-10-05T03:10:20.529144+00:00</updated>
    <content>certfr-2024-avi-0779</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2024-avi-0779"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-320682</id>
    <title>EUVD-2026-320682</title>
    <updated>2026-10-05T03:10:20.529162+00:00</updated>
    <content>EUVD-2026-320682</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-320682"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-43875</id>
    <title>fkie_cve-2024-43875</title>
    <updated>2026-10-05T03:10:20.529173+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>PCI: endpoint: Clean up error handling in vpci_scan_bus()</p>
<p>Smatch complains about inconsistent NULL checking in vpci_scan_bus():</p>
<p>drivers/pci/endpoint/functions/pci-epf-vntb.c:1024 vpci_scan_bus() error: we previously assumed 'vpci_bus' could be null (see line 1021)</p>
<p>Instead of printing an error message and then crashing we should return
an error code and clean up.</p>
<p>Also the NULL check is reversed so it prints an error for success
instead of failure.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-43875"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4g32-c2j9-mx24</id>
    <title>GHSA-4g32-c2j9-mx24</title>
    <updated>2026-10-05T03:10:20.529203+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>PCI: endpoint: Clean up error handling in vpci_scan_bus()</p>
<p>Smatch complains about inconsistent NULL checking in vpci_scan_bus():</p>
<p>drivers/pci/endpoint/functions/pci-epf-vntb.c:1024 vpci_scan_bus() error: we previously assumed 'vpci_bus' could be null (see line 1021)</p>
<p>Instead of printing an error message and then crashing we should return
an error code and clean up.</p>
<p>Also the NULL check is reversed so it prints an error for success
instead of failure.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4g32-c2j9-mx24"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2025-1097</id>
    <title>OESA-2025-1097 — kernel security update</title>
    <updated>2026-10-05T03:10:20.529223+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS: 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>ksmbd: fix potencial out-of-bounds when buffer offset is invalid</p>
<p>I found potencial out-of-bounds when buffer offset fields of a few requests
is invalid. This patch set the minimum value of buffer offset field to
-&amp;gt;Buffer offset to validate buffer length.(CVE-2024-26952)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()</p>
<p>If -&amp;gt;NameOffset of smb2_create_req is smaller than Buffer offset of
smb2_create_req, slab-out-of-bounds read can happen from smb2_open.
This patch set the minimum value of the name offset to the buffer offset
to validate name length of smb2_create_req().(CVE-2024-26954)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>fpga: bridge: add owner module and take its refcount</p>
<p>The current implementation of the fpga bridge assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the bridge if
the parent device does not have a driver.</p>
<p>To address this problem, add a module owner pointer to the fpga_bridge
struct and use it to take the module&amp;apos;s refcount. Modify the function for
registering a bridge to take an additional owner module paramet…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2025-1097"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2024:3194-1</id>
    <title>SUSE-SU-2024:3194-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-05T03:10:20.530280+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:3194-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-43875</id>
    <title>UBUNTU-CVE-2024-43875</title>
    <updated>2026-10-05T03:10:20.530563+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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 127 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: PCI: endpoint: Clean up error handling in vpci_scan_bus() Smatch complains about inconsistent NULL checking in vpci_scan_bus():     drivers/pci/endpoint/functions/pci-epf-vntb.c:1024 vpci_scan_bus() error: we previously assumed 'vpci_bus' could be null (see line 1021) Instead of printing an error message and then crashing we should return an error code and clean up. Also the NULL check is reversed so it prints an error for success instead of failure.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-43875"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1888</id>
    <title>WID-SEC-W-2024-1888 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-05T03:10:20.530748+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 oder einen unspezifischen Angriff durchzuführen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1888"/>
  </entry>
</feed>
