<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T17:29:38.737146+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2025-37907</id>
    <title>CVE-2025-37907 — accel/ivpu: Fix locking order in ivpu_job_submit</title>
    <updated>2026-11-19T17:29:38.741024+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>accel/ivpu: Fix locking order in ivpu_job_submit</p>
<p>Fix deadlock in job submission and abort handling.
When a thread aborts currently executing jobs due to a fault,
it first locks the global lock protecting submitted_jobs (#1).</p>
<p>After the last job is destroyed, it proceeds to release the related context
and locks file_priv (#2). Meanwhile, in the job submission thread,
the file_priv lock (#2) is taken first, and then the submitted_jobs
lock (#1) is obtained when a job is added to the submitted jobs list.</p>
<p>CPU0                            CPU1
       ----                    	       ----
  (for example due to a fault)         (jobs submissions keep coming)</p>
<p>lock(&amp;vdev-&gt;submitted_jobs_lock) #1
  ivpu_jobs_abort_all()
  job_destroy()
                                      lock(&amp;file_priv-&gt;lock)           #2
                                      lock(&amp;vdev-&gt;submitted_jobs_lock) #1
  file_priv_release()
  lock(&amp;vdev-&gt;context_list_lock)
  lock(&amp;file_priv-&gt;lock)           #2</p>
<p>This order of locking causes a deadlock. To resolve this issue,
change the order of locking in ivpu_job_submit().</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2025-37907"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-7649-1</id>
    <title>USN-7649-1 — linux, linux-gcp, linux-raspi, linux-realtime vulnerabilities</title>
    <updated>2026-11-19T17:29:38.741146+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:25.04: linux, Ubuntu:25.04: linux-gcp, Ubuntu:25.04: linux-raspi, Ubuntu:25.04: linux-realtime</p>
<p>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:
  - ARM64 architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Compute Acceleration Framework;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - ARM SCMI message protocol;
  - GPU drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - Multiple devices driver;
  - Network drivers;
  - PCI subsystem;
  - PTP clock framework;
  - SPI subsystem;
  - BTRFS file system;
  - SMB network file system;
  - eXpress Data Path;
  - Universal MIDI packet (UMP) support module;
  - Tracing infrastructure;
  - Memory management;
  - IPv4 networking;
  - IPv6 networking;
  - Network traffic control;
  - AMD SoC Alsa drivers;
  - SoC Audio generic drivers;
(CVE-2025-37898, CVE-2025-37990, CVE-2025-37974, CVE-2025-37991,
CVE-2025-37894, CVE-2025-37906, CVE-2025-37896, CVE-2025-37909,
CVE-2025-37923, CVE-2025-37899, CVE-2025-37901, CVE-2025-37914,
CVE-2025-38216, CVE-2025-37931, CVE-2025-37928, CVE-2025-37916,
CVE-2025-37908, CVE-2025-37915, CVE-2025-37917, CVE-2025-37921,
CVE-2025-37903, CVE-2025-37922, CVE-2025-37895, CVE-2025-37936,
CVE-2025-37933, CVE-2025-37891, CVE-2025-37926, CVE-2025-37912,
CVE-2025-37920, CVE-2025-37924, CVE-2025-37927, CVE-2025-37946,
CVE-2025-37907, CVE-2025-37930, CVE-2025-37911, CVE-2025-37905,
CVE-2025-37900, CVE-202…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-7649-1"/>
  </entry>
</feed>
