<?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:46:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23469 — drm/imagination: Synchronize interrupts before suspending the GPU</title>
      <link>https://db.gcve.eu/vuln/cve-2026-23469</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;drm/imagination: Synchronize interrupts before suspending the GPU&lt;/p&gt;
&lt;p&gt;The runtime PM suspend callback doesn&amp;#39;t know whether the IRQ handler is
in progress on a different CPU core and doesn&amp;#39;t wait for it to finish.&lt;/p&gt;
&lt;p&gt;Depending on timing, the IRQ handler could be running while the GPU is
suspended, leading to kernel crashes when trying to access GPU
registers. See example signature below.&lt;/p&gt;
&lt;p&gt;In a power off sequence initiated by the runtime PM suspend callback,
wait for any IRQ handlers in progress on other CPU cores to finish, by
calling synchronize_irq().&lt;/p&gt;
&lt;p&gt;At the same time, remove the runtime PM resume/put calls in the threaded
IRQ handler. On top of not being the right approach to begin with, and
being at the wrong place as they should have wrapped all GPU register
accesses, the driver would hit a deadlock between synchronize_irq()
being called from a runtime PM suspend callback, holding the device
power lock, and the resume callback requiring the same.&lt;/p&gt;
&lt;p&gt;Example crash signature on a TI AM68 SK platform:&lt;/p&gt;
&lt;p&gt;[  337.241218] SError Interrupt on CPU0, code 0x00000000bf000000 -- SError
  [  337.241239] CPU: 0 UID: 0 PID: 112 Comm: irq/234-gpu Tainted: G   M                6.17.7-B2C-00005-g9c7bbe4ea16c #2 PREEMPT
  [  337.241246] Tainted: [M]=MACHINE_CHECK
  [  337.241249] Hardware name: Texas Instruments AM68 SK (DT)
  [  337.241252] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
  [  337.241256] pc :…&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;drm/imagination: Synchronize interrupts before suspending the GPU&lt;/p&gt;
&lt;p&gt;The runtime PM suspend callback doesn&amp;#39;t know whether the IRQ handler is
in progress on a different CPU core and doesn&amp;#39;t wait for it to finish.&lt;/p&gt;
&lt;p&gt;Depending on timing, the IRQ handler could be running while the GPU is
suspended, leading to kernel crashes when trying to access GPU
registers. See example signature below.&lt;/p&gt;
&lt;p&gt;In a power off sequence initiated by the runtime PM suspend callback,
wait for any IRQ handlers in progress on other CPU cores to finish, by
calling synchronize_irq().&lt;/p&gt;
&lt;p&gt;At the same time, remove the runtime PM resume/put calls in the threaded
IRQ handler. On top of not being the right approach to begin with, and
being at the wrong place as they should have wrapped all GPU register
accesses, the driver would hit a deadlock between synchronize_irq()
being called from a runtime PM suspend callback, holding the device
power lock, and the resume callback requiring the same.&lt;/p&gt;
&lt;p&gt;Example crash signature on a TI AM68 SK platform:&lt;/p&gt;
&lt;p&gt;[  337.241218] SError Interrupt on CPU0, code 0x00000000bf000000 -- SError
  [  337.241239] CPU: 0 UID: 0 PID: 112 Comm: irq/234-gpu Tainted: G   M                6.17.7-B2C-00005-g9c7bbe4ea16c #2 PREEMPT
  [  337.241246] Tainted: [M]=MACHINE_CHECK
  [  337.241249] Hardware name: Texas Instruments AM68 SK (DT)
  [  337.241252] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
  [  337.241256] pc :…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-23469</guid>
    </item>
    <item>
      <title>USN-8729-1 — linux, linux-fips, linux-gcp, linux-gcp-fips, linux-gke, linux-gkeop, linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowl…</title>
      <link>https://db.gcve.eu/vuln/usn-8729-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-nvidia-6.8, Ubuntu:Pro:Realtime:22.04:LTS: linux-realtime-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-gkeop, Ubuntu:24.04:LTS: linux-nvidia, Ubuntu:24.04:LTS: linux-nvidia-lowlatency, Ubuntu:24.04:LTS: linux-raspi, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime and 2 more&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:
  - ARM32 architecture;
  - ARM64 architecture;
  - PowerPC architecture;
  - Compute Acceleration Framework;
  - Drivers core;
  - Bluetooth drivers;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - EFI core;
  - GPU drivers;
  - Hardware monitoring drivers;
  - InfiniBand drivers;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - SCSI subsystem;
  - SPI subsystem;
  - Network file systems library;
  - NTFS3 file system;
  - SMB network file system;
  - File systems infrastructure;
  - Software nodes and device properties;
  - Bluetooth subsystem;
  - Netfilter;
  - Tracing infrastructure;
  - io_uring subsystem;
  - IRQ subsystem;
  - KProbes tracing;
  - Memory management;
  - B.A.T.M.A.N. meshing protocol;
  - Ethernet bridge;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - Multipath TCP;
  - Phonet protocol;
  - SMC sockets;
  - TLS protocol;
  - Unix domain sockets;
  - VMware vSockets driver;
  - Wireless networking;
  - Key management;
  - Linux Security Modules (LSM) Framework;
  - ALSA framework;
  - AudioScience HPI driver;
(CVE-2025-71289, CVE-2026-23469, CVE-2026-31420, CVE-2026-31486,
CVE-2026-31560, CVE-2026-46158, CVE-2026-46170, CVE-2026-46275,
CVE-2026-46315, CVE-2026-52912, CVE-2026-52915, CVE-2026-52916,
CVE-2026-52918, CVE-2026-52919…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-nvidia-6.8, Ubuntu:Pro:Realtime:22.04:LTS: linux-realtime-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-gkeop, Ubuntu:24.04:LTS: linux-nvidia, Ubuntu:24.04:LTS: linux-nvidia-lowlatency, Ubuntu:24.04:LTS: linux-raspi, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime and 2 more&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:
  - ARM32 architecture;
  - ARM64 architecture;
  - PowerPC architecture;
  - Compute Acceleration Framework;
  - Drivers core;
  - Bluetooth drivers;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - EFI core;
  - GPU drivers;
  - Hardware monitoring drivers;
  - InfiniBand drivers;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - SCSI subsystem;
  - SPI subsystem;
  - Network file systems library;
  - NTFS3 file system;
  - SMB network file system;
  - File systems infrastructure;
  - Software nodes and device properties;
  - Bluetooth subsystem;
  - Netfilter;
  - Tracing infrastructure;
  - io_uring subsystem;
  - IRQ subsystem;
  - KProbes tracing;
  - Memory management;
  - B.A.T.M.A.N. meshing protocol;
  - Ethernet bridge;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - Multipath TCP;
  - Phonet protocol;
  - SMC sockets;
  - TLS protocol;
  - Unix domain sockets;
  - VMware vSockets driver;
  - Wireless networking;
  - Key management;
  - Linux Security Modules (LSM) Framework;
  - ALSA framework;
  - AudioScience HPI driver;
(CVE-2025-71289, CVE-2026-23469, CVE-2026-31420, CVE-2026-31486,
CVE-2026-31560, CVE-2026-46158, CVE-2026-46170, CVE-2026-46275,
CVE-2026-46315, CVE-2026-52912, CVE-2026-52915, CVE-2026-52916,
CVE-2026-52918, CVE-2026-52919…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8729-1</guid>
    </item>
  </channel>
</rss>
