<?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:35:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90311 — thermal: hwmon: Remove hwmon class device along with its parent</title>
      <link>https://db.gcve.eu/vuln/cve-2026-90311</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;thermal: hwmon: Remove hwmon class device along with its parent&lt;/p&gt;
&lt;p&gt;The current code creates one hwmon device per thermal zone type and that
device is registered under the first thermal zone of the given type.&lt;/p&gt;
&lt;p&gt;That turns out to be problematic when the thermal zone holding the
hwmon device is removed.&lt;/p&gt;
&lt;p&gt;For example, say that there are two ACPI thermal zones on a system&lt;/p&gt;
&lt;p&gt;/sys/devices/virtual/thermal/thermal_zone0/
 /sys/devices/virtual/thermal/thermal_zone1/&lt;/p&gt;
&lt;p&gt;The current code registers a hwmon class device for thermal_zone0 only:&lt;/p&gt;
&lt;p&gt;/sys/devices/virtual/thermal/thermal_zone0/hwmon0/&lt;/p&gt;
&lt;p&gt;because the type is &amp;#34;acpitz&amp;#34; for both of them, but it adds a sysfs
attribute that belongs to thermal_zone1 under it:&lt;/p&gt;
&lt;p&gt;/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp2_input&lt;/p&gt;
&lt;p&gt;There is also&lt;/p&gt;
&lt;p&gt;/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input&lt;/p&gt;
&lt;p&gt;which belongs to thermal_zone0.&lt;/p&gt;
&lt;p&gt;When thermal_zone0 is removed, say because the ACPI thermal driver is
unbound from the underlying platform device, thermal_remove_hwmon_sysfs()
skips the removal of hwmon0 because of the temp2_input attribute
belonging to thermal_zone1 which effectively prevents thermal_zone0
removal from making progress.&lt;/p&gt;
&lt;p&gt;Address this by making thermal_remove_hwmon_sysfs() remove the entire
hwmon class device interface for the given thermal zone type when the
thermal zone device holding it is removed.&lt;/p&gt;
&lt;p&gt;To prevent races with thermal_add_hwmon_sysfs() that may i…&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;thermal: hwmon: Remove hwmon class device along with its parent&lt;/p&gt;
&lt;p&gt;The current code creates one hwmon device per thermal zone type and that
device is registered under the first thermal zone of the given type.&lt;/p&gt;
&lt;p&gt;That turns out to be problematic when the thermal zone holding the
hwmon device is removed.&lt;/p&gt;
&lt;p&gt;For example, say that there are two ACPI thermal zones on a system&lt;/p&gt;
&lt;p&gt;/sys/devices/virtual/thermal/thermal_zone0/
 /sys/devices/virtual/thermal/thermal_zone1/&lt;/p&gt;
&lt;p&gt;The current code registers a hwmon class device for thermal_zone0 only:&lt;/p&gt;
&lt;p&gt;/sys/devices/virtual/thermal/thermal_zone0/hwmon0/&lt;/p&gt;
&lt;p&gt;because the type is &amp;#34;acpitz&amp;#34; for both of them, but it adds a sysfs
attribute that belongs to thermal_zone1 under it:&lt;/p&gt;
&lt;p&gt;/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp2_input&lt;/p&gt;
&lt;p&gt;There is also&lt;/p&gt;
&lt;p&gt;/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input&lt;/p&gt;
&lt;p&gt;which belongs to thermal_zone0.&lt;/p&gt;
&lt;p&gt;When thermal_zone0 is removed, say because the ACPI thermal driver is
unbound from the underlying platform device, thermal_remove_hwmon_sysfs()
skips the removal of hwmon0 because of the temp2_input attribute
belonging to thermal_zone1 which effectively prevents thermal_zone0
removal from making progress.&lt;/p&gt;
&lt;p&gt;Address this by making thermal_remove_hwmon_sysfs() remove the entire
hwmon class device interface for the given thermal zone type when the
thermal zone device holding it is removed.&lt;/p&gt;
&lt;p&gt;To prevent races with thermal_add_hwmon_sysfs() that may i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-90311</guid>
    </item>
    <item>
      <title>USN-8959-1 — linux, linux-aws, linux-gcp, linux-hwe-7.0, linux-ibm, linux-oracle vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8959-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - USB Gadget drivers;
  - Memory management;
  - Multiple devices driver;
  - ARM64 architecture;
  - EROFS file system;
  - Networking core;
  - eXpress Data Path;
  - ARM32 architecture;
  - M68K architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - Speakup Console Speech Driver;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - Micron PCIe SSD driver;
  - Null block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - AMD CDX bus driver;
  - Hardware random number generator core;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU frequency scaling framework;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - USB Gadget drivers;
  - Memory management;
  - Multiple devices driver;
  - ARM64 architecture;
  - EROFS file system;
  - Networking core;
  - eXpress Data Path;
  - ARM32 architecture;
  - M68K architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - Speakup Console Speech Driver;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - Micron PCIe SSD driver;
  - Null block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - AMD CDX bus driver;
  - Hardware random number generator core;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU frequency scaling framework;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8959-1</guid>
    </item>
  </channel>
</rss>
