<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 03:52:50 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12787</title>
      <link>https://db.gcve.eu/vuln/bdu:2025-12787</link>
      <description>bdu:2025-12787</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/bdu:2025-12787</guid>
    </item>
    <item>
      <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>
      <link>https://db.gcve.eu/vuln/certfr-2025-avi-0895</link>
      <description>certfr-2025-avi-0895</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2025-avi-0895</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53515</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2023-53515</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;virtio-mmio: don&amp;#39;t break lifecycle of vm_dev&lt;/p&gt;
&lt;p&gt;vm_dev has a separate lifecycle because it has a &amp;#39;struct device&amp;#39;
embedded. Thus, having a release callback for it is correct.&lt;/p&gt;
&lt;p&gt;Allocating the vm_dev struct with devres totally breaks this protection,
though. Instead of waiting for the vm_dev release callback, the memory
is freed when the platform_device is removed. Resulting in a
use-after-free when finally the callback is to be called.&lt;/p&gt;
&lt;p&gt;To easily see the problem, compile the kernel with
CONFIG_DEBUG_KOBJECT_RELEASE and unbind with sysfs.&lt;/p&gt;
&lt;p&gt;The fix is easy, don&amp;#39;t use devres in this case.&lt;/p&gt;
&lt;p&gt;Found during my research about object lifetime problems.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;virtio-mmio: don&amp;#39;t break lifecycle of vm_dev&lt;/p&gt;
&lt;p&gt;vm_dev has a separate lifecycle because it has a &amp;#39;struct device&amp;#39;
embedded. Thus, having a release callback for it is correct.&lt;/p&gt;
&lt;p&gt;Allocating the vm_dev struct with devres totally breaks this protection,
though. Instead of waiting for the vm_dev release callback, the memory
is freed when the platform_device is removed. Resulting in a
use-after-free when finally the callback is to be called.&lt;/p&gt;
&lt;p&gt;To easily see the problem, compile the kernel with
CONFIG_DEBUG_KOBJECT_RELEASE and unbind with sysfs.&lt;/p&gt;
&lt;p&gt;The fix is easy, don&amp;#39;t use devres in this case.&lt;/p&gt;
&lt;p&gt;Found during my research about object lifetime problems.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2023-53515</guid>
    </item>
    <item>
      <title>GHSA-h7xx-83rf-fcj5</title>
      <link>https://db.gcve.eu/vuln/ghsa-h7xx-83rf-fcj5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;virtio-mmio: don&amp;#39;t break lifecycle of vm_dev&lt;/p&gt;
&lt;p&gt;vm_dev has a separate lifecycle because it has a &amp;#39;struct device&amp;#39;
embedded. Thus, having a release callback for it is correct.&lt;/p&gt;
&lt;p&gt;Allocating the vm_dev struct with devres totally breaks this protection,
though. Instead of waiting for the vm_dev release callback, the memory
is freed when the platform_device is removed. Resulting in a
use-after-free when finally the callback is to be called.&lt;/p&gt;
&lt;p&gt;To easily see the problem, compile the kernel with
CONFIG_DEBUG_KOBJECT_RELEASE and unbind with sysfs.&lt;/p&gt;
&lt;p&gt;The fix is easy, don&amp;#39;t use devres in this case.&lt;/p&gt;
&lt;p&gt;Found during my research about object lifetime problems.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;virtio-mmio: don&amp;#39;t break lifecycle of vm_dev&lt;/p&gt;
&lt;p&gt;vm_dev has a separate lifecycle because it has a &amp;#39;struct device&amp;#39;
embedded. Thus, having a release callback for it is correct.&lt;/p&gt;
&lt;p&gt;Allocating the vm_dev struct with devres totally breaks this protection,
though. Instead of waiting for the vm_dev release callback, the memory
is freed when the platform_device is removed. Resulting in a
use-after-free when finally the callback is to be called.&lt;/p&gt;
&lt;p&gt;To easily see the problem, compile the kernel with
CONFIG_DEBUG_KOBJECT_RELEASE and unbind with sysfs.&lt;/p&gt;
&lt;p&gt;The fix is easy, don&amp;#39;t use devres in this case.&lt;/p&gt;
&lt;p&gt;Found during my research about object lifetime problems.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-h7xx-83rf-fcj5</guid>
    </item>
    <item>
      <title>OESA-2025-2469 — kernel security update</title>
      <link>https://db.gcve.eu/vuln/oesa-2025-2469</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFSD: Protect against send buffer overflow in NFSv2 READ&lt;/p&gt;
&lt;p&gt;Since before the git era, NFSD has conserved the number of pages
held by each nfsd thread by combining the RPC receive and send
buffers into a single array of pages. This works because there are
no cases where an operation needs a large RPC Call message and a
large RPC Reply at the same time.&lt;/p&gt;
&lt;p&gt;Once an RPC Call has been received, svc_process() updates
svc_rqst::rq_res to describe the part of rq_pages that can be
used for constructing the Reply. This means that the send buffer
(rq_res) shrinks when the received RPC record containing the RPC
Call is large.&lt;/p&gt;
&lt;p&gt;A client can force this shrinkage on TCP by sending a correctly-
formed RPC Call header contained in an RPC record that is
excessively large. The full maximum payload size cannot be
constructed in that case.(CVE-2022-50410)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: az6007: Fix null-ptr-deref in az6007_i2c_xfer()&lt;/p&gt;
&lt;p&gt;In az6007_i2c_xfer, msg is controlled by user. When msg[i].buf
is null and msg[i].len is zero, former checks on msg[i].buf would be
passed. Malicious data finally reach az6007_i2c_xfer. If accessing
msg[i].buf[0] without sanity check, null ptr deref would happen.
We add check on msg[i].len to prevent crash.&lt;/p&gt;
&lt;p&gt;Similar commit:
commit 0ed554fd769a
(&amp;amp;quot;media: dvb-usb: az6027: fix null-p…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFSD: Protect against send buffer overflow in NFSv2 READ&lt;/p&gt;
&lt;p&gt;Since before the git era, NFSD has conserved the number of pages
held by each nfsd thread by combining the RPC receive and send
buffers into a single array of pages. This works because there are
no cases where an operation needs a large RPC Call message and a
large RPC Reply at the same time.&lt;/p&gt;
&lt;p&gt;Once an RPC Call has been received, svc_process() updates
svc_rqst::rq_res to describe the part of rq_pages that can be
used for constructing the Reply. This means that the send buffer
(rq_res) shrinks when the received RPC record containing the RPC
Call is large.&lt;/p&gt;
&lt;p&gt;A client can force this shrinkage on TCP by sending a correctly-
formed RPC Call header contained in an RPC record that is
excessively large. The full maximum payload size cannot be
constructed in that case.(CVE-2022-50410)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: az6007: Fix null-ptr-deref in az6007_i2c_xfer()&lt;/p&gt;
&lt;p&gt;In az6007_i2c_xfer, msg is controlled by user. When msg[i].buf
is null and msg[i].len is zero, former checks on msg[i].buf would be
passed. Malicious data finally reach az6007_i2c_xfer. If accessing
msg[i].buf[0] without sanity check, null ptr deref would happen.
We add check on msg[i].len to prevent crash.&lt;/p&gt;
&lt;p&gt;Similar commit:
commit 0ed554fd769a
(&amp;amp;quot;media: dvb-usb: az6027: fix null-p…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/oesa-2025-2469</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03600-1 — Security update for the Linux Kernel</title>
      <link>https://db.gcve.eu/vuln/suse-su-2025:03600-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/suse-su-2025:03600-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53515</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2023-53515</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: virtio-mmio: don&amp;#39;t break lifecycle of vm_dev vm_dev has a separate lifecycle because it has a &amp;#39;struct device&amp;#39; embedded. Thus, having a release callback for it is correct. Allocating the vm_dev struct with devres totally breaks this protection, though. Instead of waiting for the vm_dev release callback, the memory is freed when the platform_device is removed. Resulting in a use-after-free when finally the callback is to be called. To easily see the problem, compile the kernel with CONFIG_DEBUG_KOBJECT_RELEASE and unbind with sysfs. The fix is easy, don&amp;#39;t use devres in this case. Found during my research about object lifetime problems.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: virtio-mmio: don&amp;#39;t break lifecycle of vm_dev vm_dev has a separate lifecycle because it has a &amp;#39;struct device&amp;#39; embedded. Thus, having a release callback for it is correct. Allocating the vm_dev struct with devres totally breaks this protection, though. Instead of waiting for the vm_dev release callback, the memory is freed when the platform_device is removed. Resulting in a use-after-free when finally the callback is to be called. To easily see the problem, compile the kernel with CONFIG_DEBUG_KOBJECT_RELEASE and unbind with sysfs. The fix is easy, don&amp;#39;t use devres in this case. Found during my research about object lifetime problems.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2023-53515</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2187 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2025-2187</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2025-2187</guid>
    </item>
  </channel>
</rss>
