<?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>Thu, 19 Nov 2026 17:58:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52439 — uio: Fix use-after-free in uio_open</title>
      <link>https://db.gcve.eu/vuln/cve-2023-52439</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;uio: Fix use-after-free in uio_open&lt;/p&gt;
&lt;p&gt;core-1				core-2
-------------------------------------------------------
uio_unregister_device		uio_open
				idev = idr_find()
device_unregister(&amp;amp;idev-&amp;gt;dev)
put_device(&amp;amp;idev-&amp;gt;dev)
uio_device_release
				get_device(&amp;amp;idev-&amp;gt;dev)
kfree(idev)
uio_free_minor(minor)
				uio_release
				put_device(&amp;amp;idev-&amp;gt;dev)
				kfree(idev)
-------------------------------------------------------&lt;/p&gt;
&lt;p&gt;In the core-1 uio_unregister_device(), the device_unregister will kfree
idev when the idev-&amp;gt;dev kobject ref is 1. But after core-1
device_unregister, put_device and before doing kfree, the core-2 may
get_device. Then:
1. After core-1 kfree idev, the core-2 will do use-after-free for idev.
2. When core-2 do uio_release and put_device, the idev will be double
   freed.&lt;/p&gt;
&lt;p&gt;To address this issue, we can get idev atomic &amp;amp; inc idev reference with
minor_lock.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;uio: Fix use-after-free in uio_open&lt;/p&gt;
&lt;p&gt;core-1				core-2
-------------------------------------------------------
uio_unregister_device		uio_open
				idev = idr_find()
device_unregister(&amp;amp;idev-&amp;gt;dev)
put_device(&amp;amp;idev-&amp;gt;dev)
uio_device_release
				get_device(&amp;amp;idev-&amp;gt;dev)
kfree(idev)
uio_free_minor(minor)
				uio_release
				put_device(&amp;amp;idev-&amp;gt;dev)
				kfree(idev)
-------------------------------------------------------&lt;/p&gt;
&lt;p&gt;In the core-1 uio_unregister_device(), the device_unregister will kfree
idev when the idev-&amp;gt;dev kobject ref is 1. But after core-1
device_unregister, put_device and before doing kfree, the core-2 may
get_device. Then:
1. After core-1 kfree idev, the core-2 will do use-after-free for idev.
2. When core-2 do uio_release and put_device, the idev will be double
   freed.&lt;/p&gt;
&lt;p&gt;To address this issue, we can get idev atomic &amp;amp; inc idev reference with
minor_lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2023-52439</guid>
    </item>
    <item>
      <title>USN-6688-1 — linux-oem-6.1 vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-6688-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-oem-6.1&lt;/p&gt;
&lt;p&gt;Pratyush Yadav discovered that the Xen network backend implementation in
the Linux kernel did not properly handle zero length data request, leading
to a null pointer dereference vulnerability. An attacker in a guest VM
could possibly use this to cause a denial of service (host domain crash).
(CVE-2023-46838)&lt;/p&gt;
&lt;p&gt;It was discovered that the Habana&amp;#39;s AI Processors driver in the Linux
kernel did not properly initialize certain data structures before passing
them to user space. A local attacker could use this to expose sensitive
information (kernel memory). (CVE-2023-50431)&lt;/p&gt;
&lt;p&gt;Murray McAllister discovered that the VMware Virtual GPU DRM driver in the
Linux kernel did not properly handle memory objects when storing surfaces,
leading to a use-after-free vulnerability. A local attacker in a guest VM
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2023-5633)&lt;/p&gt;
&lt;p&gt;It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly validate certain SMB messages, leading to an
out-of-bounds read vulnerability. An attacker could use this to cause a
denial of service (system crash) or possibly expose sensitive information.
(CVE-2023-6610)&lt;/p&gt;
&lt;p&gt;It was discovered that the VirtIO subsystem in the Linux kernel did not
properly initialize memory in some situations. A local attacker could use
this to possibly expose sensitive information (kernel memory).
(CVE-2024-0340)&lt;/p&gt;
&lt;p&gt;Lonial Con discovered that the netfilter subsystem…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-oem-6.1&lt;/p&gt;
&lt;p&gt;Pratyush Yadav discovered that the Xen network backend implementation in
the Linux kernel did not properly handle zero length data request, leading
to a null pointer dereference vulnerability. An attacker in a guest VM
could possibly use this to cause a denial of service (host domain crash).
(CVE-2023-46838)&lt;/p&gt;
&lt;p&gt;It was discovered that the Habana&amp;#39;s AI Processors driver in the Linux
kernel did not properly initialize certain data structures before passing
them to user space. A local attacker could use this to expose sensitive
information (kernel memory). (CVE-2023-50431)&lt;/p&gt;
&lt;p&gt;Murray McAllister discovered that the VMware Virtual GPU DRM driver in the
Linux kernel did not properly handle memory objects when storing surfaces,
leading to a use-after-free vulnerability. A local attacker in a guest VM
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2023-5633)&lt;/p&gt;
&lt;p&gt;It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly validate certain SMB messages, leading to an
out-of-bounds read vulnerability. An attacker could use this to cause a
denial of service (system crash) or possibly expose sensitive information.
(CVE-2023-6610)&lt;/p&gt;
&lt;p&gt;It was discovered that the VirtIO subsystem in the Linux kernel did not
properly initialize memory in some situations. A local attacker could use
this to possibly expose sensitive information (kernel memory).
(CVE-2024-0340)&lt;/p&gt;
&lt;p&gt;Lonial Con discovered that the netfilter subsystem…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-6688-1</guid>
    </item>
  </channel>
</rss>
