<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 00:45:45 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-37907</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-37907</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-37907</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0625 — De multiples vulnérabilités ont été découvertes dans Ubuntu Ubuntu. Certaines d'entre elles permettent à un attaquant d…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0625</link>
      <description>certfr-2025-avi-0625</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0625</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37907</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37907</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 122 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Fix locking order in ivpu_job_submit 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). 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.        CPU0                            CPU1        ----                    	       ----   (for example due to a fault)         (jobs submissions keep coming)   lock(&amp;amp;vdev-&amp;gt;submitted_jobs_lock) #1   ivpu_jobs_abort_all()   job_destroy()                                       lock(&amp;amp;file_priv-&amp;gt;lock)           #2                                       lock(&amp;amp;vdev-&amp;gt;submitted_jobs_lock) #1   file_priv_release()   lock(&amp;amp;vdev-&amp;gt;context_list_lock)   lock(&amp;amp;file_priv-&amp;gt;lock)           #2 This order of locking causes a deadlock. To resolve this issue, change the order of locking in ivpu_job_submit().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 122 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Fix locking order in ivpu_job_submit 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). 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.        CPU0                            CPU1        ----                    	       ----   (for example due to a fault)         (jobs submissions keep coming)   lock(&amp;amp;vdev-&amp;gt;submitted_jobs_lock) #1   ivpu_jobs_abort_all()   job_destroy()                                       lock(&amp;amp;file_priv-&amp;gt;lock)           #2                                       lock(&amp;amp;vdev-&amp;gt;submitted_jobs_lock) #1   file_priv_release()   lock(&amp;amp;vdev-&amp;gt;context_list_lock)   lock(&amp;amp;file_priv-&amp;gt;lock)           #2 This order of locking causes a deadlock. To resolve this issue, change the order of locking in ivpu_job_submit().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37907</guid>
    </item>
  </channel>
</rss>
