<?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:25:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26933 — USB: core: Fix deadlock in port "disable" sysfs attribute</title>
      <link>https://db.gcve.eu/vuln/cve-2024-26933</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;USB: core: Fix deadlock in port &amp;#34;disable&amp;#34; sysfs attribute&lt;/p&gt;
&lt;p&gt;The show and store callback routines for the &amp;#34;disable&amp;#34; sysfs attribute
file in port.c acquire the device lock for the port&amp;#39;s parent hub
device.  This can cause problems if another process has locked the hub
to remove it or change its configuration:&lt;/p&gt;
&lt;p&gt;Removing the hub or changing its configuration requires the
	hub interface to be removed, which requires the port device
	to be removed, and device_del() waits until all outstanding
	sysfs attribute callbacks for the ports have returned.  The
	lock can&amp;#39;t be released until then.&lt;/p&gt;
&lt;p&gt;But the disable_show() or disable_store() routine can&amp;#39;t return
	until after it has acquired the lock.&lt;/p&gt;
&lt;p&gt;The resulting deadlock can be avoided by calling
sysfs_break_active_protection().  This will cause the sysfs core not
to wait for the attribute&amp;#39;s callback routine to return, allowing the
removal to proceed.  The disadvantage is that after making this call,
there is no guarantee that the hub structure won&amp;#39;t be deallocated at
any moment.  To prevent this, we have to acquire a reference to it
first by calling hub_get().&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;USB: core: Fix deadlock in port &amp;#34;disable&amp;#34; sysfs attribute&lt;/p&gt;
&lt;p&gt;The show and store callback routines for the &amp;#34;disable&amp;#34; sysfs attribute
file in port.c acquire the device lock for the port&amp;#39;s parent hub
device.  This can cause problems if another process has locked the hub
to remove it or change its configuration:&lt;/p&gt;
&lt;p&gt;Removing the hub or changing its configuration requires the
	hub interface to be removed, which requires the port device
	to be removed, and device_del() waits until all outstanding
	sysfs attribute callbacks for the ports have returned.  The
	lock can&amp;#39;t be released until then.&lt;/p&gt;
&lt;p&gt;But the disable_show() or disable_store() routine can&amp;#39;t return
	until after it has acquired the lock.&lt;/p&gt;
&lt;p&gt;The resulting deadlock can be avoided by calling
sysfs_break_active_protection().  This will cause the sysfs core not
to wait for the attribute&amp;#39;s callback routine to return, allowing the
removal to proceed.  The disadvantage is that after making this call,
there is no guarantee that the hub structure won&amp;#39;t be deallocated at
any moment.  To prevent this, we have to acquire a reference to it
first by calling hub_get().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-26933</guid>
    </item>
    <item>
      <title>USN-6816-1 — linux, linux-ibm, linux-lowlatency, linux-raspi vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-6816-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-lowlatency, Ubuntu:24.04:LTS: linux-raspi&lt;/p&gt;
&lt;p&gt;Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not
properly handle certain error conditions, leading to a NULL pointer
dereference. A local attacker could possibly trigger this vulnerability to
cause a denial of service. (CVE-2022-38096)&lt;/p&gt;
&lt;p&gt;Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux
kernel contained a race condition during device removal, leading to a use-
after-free vulnerability. A physically proximate attacker could possibly
use this to cause a denial of service (system crash). (CVE-2023-47233)&lt;/p&gt;
&lt;p&gt;It was discovered that the ATA over Ethernet (AoE) driver in the Linux
kernel contained a race condition, leading to a use-after-free
vulnerability. An attacker could use this to cause a denial of service or
possibly execute arbitrary code. (CVE-2023-6270)&lt;/p&gt;
&lt;p&gt;It was discovered that the Atheros 802.11ac wireless driver did not
properly validate certain data structures, leading to a NULL pointer
dereference. An attacker could possibly use this to cause a denial of
service. (CVE-2023-7042)&lt;/p&gt;
&lt;p&gt;It was discovered that the Intel Data Streaming and Intel Analytics
Accelerator drivers in the Linux kernel allowed direct access to the
devices for unprivileged users and virtual machines. A local attacker could
use this to cause a denial of service. (CVE-2024-21823)&lt;/p&gt;
&lt;p&gt;Gui-Dong Han discovered that the software RAID driver in the Linux kernel
contained a race condition, leading to an integer overflow vulnerability. A
privileged attacker could possib…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-lowlatency, Ubuntu:24.04:LTS: linux-raspi&lt;/p&gt;
&lt;p&gt;Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not
properly handle certain error conditions, leading to a NULL pointer
dereference. A local attacker could possibly trigger this vulnerability to
cause a denial of service. (CVE-2022-38096)&lt;/p&gt;
&lt;p&gt;Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux
kernel contained a race condition during device removal, leading to a use-
after-free vulnerability. A physically proximate attacker could possibly
use this to cause a denial of service (system crash). (CVE-2023-47233)&lt;/p&gt;
&lt;p&gt;It was discovered that the ATA over Ethernet (AoE) driver in the Linux
kernel contained a race condition, leading to a use-after-free
vulnerability. An attacker could use this to cause a denial of service or
possibly execute arbitrary code. (CVE-2023-6270)&lt;/p&gt;
&lt;p&gt;It was discovered that the Atheros 802.11ac wireless driver did not
properly validate certain data structures, leading to a NULL pointer
dereference. An attacker could possibly use this to cause a denial of
service. (CVE-2023-7042)&lt;/p&gt;
&lt;p&gt;It was discovered that the Intel Data Streaming and Intel Analytics
Accelerator drivers in the Linux kernel allowed direct access to the
devices for unprivileged users and virtual machines. A local attacker could
use this to cause a denial of service. (CVE-2024-21823)&lt;/p&gt;
&lt;p&gt;Gui-Dong Han discovered that the software RAID driver in the Linux kernel
contained a race condition, leading to an integer overflow vulnerability. A
privileged attacker could possib…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-6816-1</guid>
    </item>
  </channel>
</rss>
