<?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-05T01:09:40.919300+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-04345</id>
    <title>bdu:2025-04345</title>
    <updated>2026-10-05T01:09:41.419411+00:00</updated>
    <content>bdu:2025-04345</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-04345"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</id>
    <title>certfr-2025-avi-0252 — 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-05T01:09:41.419495+00:00</updated>
    <content>certfr-2025-avi-0252</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2025-04672</id>
    <title>cnvd-2025-04672</title>
    <updated>2026-10-05T01:09:41.419518+00:00</updated>
    <content>cnvd-2025-04672</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2025-04672"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-309861</id>
    <title>EUVD-2026-309861</title>
    <updated>2026-10-05T01:09:41.419532+00:00</updated>
    <content>EUVD-2026-309861</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-309861"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47653</id>
    <title>fkie_cve-2021-47653</title>
    <updated>2026-10-05T01:09:41.419544+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>media: davinci: vpif: fix use-after-free on driver unbind</p>
<p>The driver allocates and registers two platform device structures during
probe, but the devices were never deregistered on driver unbind.</p>
<p>This results in a use-after-free on driver unbind as the device
structures were allocated using devres and would be freed by driver
core when remove() returns.</p>
<p>Fix this by adding the missing deregistration calls to the remove()
callback and failing probe on registration errors.</p>
<p>Note that the platform device structures must be freed using a proper
release callback to avoid leaking associated resources like device
names.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-47653"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9rg5-7j22-7fqw</id>
    <title>GHSA-9rg5-7j22-7fqw</title>
    <updated>2026-10-05T01:09:41.419582+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>media: davinci: vpif: fix use-after-free on driver unbind</p>
<p>The driver allocates and registers two platform device structures during
probe, but the devices were never deregistered on driver unbind.</p>
<p>This results in a use-after-free on driver unbind as the device
structures were allocated using devres and would be freed by driver
core when remove() returns.</p>
<p>Fix this by adding the missing deregistration calls to the remove()
callback and failing probe on registration errors.</p>
<p>Note that the platform device structures must be freed using a proper
release callback to avoid leaking associated resources like device
names.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9rg5-7j22-7fqw"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2025-2772</id>
    <title>OESA-2025-2772 — kernel security update</title>
    <updated>2026-10-05T01:09:41.419604+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>media: davinci: vpif: fix use-after-free on driver unbind</p>
<p>The driver allocates and registers two platform device structures during
probe, but the devices were never deregistered on driver unbind.</p>
<p>This results in a use-after-free on driver unbind as the device
structures were allocated using devres and would be freed by driver
core when remove() returns.</p>
<p>Fix this by adding the missing deregistration calls to the remove()
callback and failing probe on registration errors.</p>
<p>Note that the platform device structures must be freed using a proper
release callback to avoid leaking associated resources like device
names.(CVE-2021-47653)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mmc: core: use sysfs_emit() instead of sprintf()</p>
<p>sprintf() (still used in the MMC core for the sysfs output) is vulnerable
to the buffer overflow.  Use the new-fangled sysfs_emit() instead.</p>
<p>Found by Linux Verification Center (linuxtesting.org) with the SVACE static
analysis tool.(CVE-2022-49267)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>Bluetooth: btmtksdio: fix use-after-free at btmtksdio_recv_event</p>
<p>We should not access skb buffer data anymore after hci_recv_frame was
called.</p>
<p>[   39.634809] BUG: KASAN: use-after-free in btmtksdio_recv_event+0x1b0
[   39.634855] Read of size 1 at addr ffffff80cf28a60d by tas…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2025-2772"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2025:1176-1</id>
    <title>SUSE-SU-2025:1176-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-05T01:09:41.419718+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:1176-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47653</id>
    <title>UBUNTU-CVE-2021-47653</title>
    <updated>2026-10-05T01:09:41.420075+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 92 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: media: davinci: vpif: fix use-after-free on driver unbind The driver allocates and registers two platform device structures during probe, but the devices were never deregistered on driver unbind. This results in a use-after-free on driver unbind as the device structures were allocated using devres and would be freed by driver core when remove() returns. Fix this by adding the missing deregistration calls to the remove() callback and failing probe on registration errors. Note that the platform device structures must be freed using a proper release callback to avoid leaking associated resources like device names.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47653"/>
  </entry>
</feed>
