<?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 07:46:12 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-40130</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-40130</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-40130</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0128 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0128</link>
      <description>certfr-2026-avi-0128</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0128</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-40130</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-40130</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 103 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix data race in CPU latency PM QoS request handling The cpu_latency_qos_add/remove/update_request interfaces lack internal synchronization by design, requiring the caller to ensure thread safety. The current implementation relies on the &amp;#39;pm_qos_enabled&amp;#39; flag, which is insufficient to prevent concurrent access and cannot serve as a proper synchronization mechanism. This has led to data races and list corruption issues. A typical race condition call trace is: [Thread A] ufshcd_pm_qos_exit()   --&amp;gt; cpu_latency_qos_remove_request()     --&amp;gt; cpu_latency_qos_apply();       --&amp;gt; pm_qos_update_target()         --&amp;gt; plist_del              &amp;lt;--(1) delete plist node     --&amp;gt; memset(req, 0, sizeof(*req));   --&amp;gt; hba-&amp;gt;pm_qos_enabled = false; [Thread B] ufshcd_devfreq_target   --&amp;gt; ufshcd_devfreq_scale     --&amp;gt; ufshcd_scale_clks       --&amp;gt; ufshcd_pm_qos_update     &amp;lt;--(2) pm_qos_enabled is true         --&amp;gt; cpu_latency_qos_update_request           --&amp;gt; pm_qos_update_target             --&amp;gt; plist_del          &amp;lt;--(3) plist node use-after-free Introduces a dedicated mutex to serialize PM QoS operations, preventing data races and ensuring safe access to PM QoS resources, including sysfs interface reads.&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 103 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix data race in CPU latency PM QoS request handling The cpu_latency_qos_add/remove/update_request interfaces lack internal synchronization by design, requiring the caller to ensure thread safety. The current implementation relies on the &amp;#39;pm_qos_enabled&amp;#39; flag, which is insufficient to prevent concurrent access and cannot serve as a proper synchronization mechanism. This has led to data races and list corruption issues. A typical race condition call trace is: [Thread A] ufshcd_pm_qos_exit()   --&amp;gt; cpu_latency_qos_remove_request()     --&amp;gt; cpu_latency_qos_apply();       --&amp;gt; pm_qos_update_target()         --&amp;gt; plist_del              &amp;lt;--(1) delete plist node     --&amp;gt; memset(req, 0, sizeof(*req));   --&amp;gt; hba-&amp;gt;pm_qos_enabled = false; [Thread B] ufshcd_devfreq_target   --&amp;gt; ufshcd_devfreq_scale     --&amp;gt; ufshcd_scale_clks       --&amp;gt; ufshcd_pm_qos_update     &amp;lt;--(2) pm_qos_enabled is true         --&amp;gt; cpu_latency_qos_update_request           --&amp;gt; pm_qos_update_target             --&amp;gt; plist_del          &amp;lt;--(3) plist node use-after-free Introduces a dedicated mutex to serialize PM QoS operations, preventing data races and ensuring safe access to PM QoS resources, including sysfs interface reads.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-40130</guid>
    </item>
  </channel>
</rss>
