<?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://cve.radiocsirt.org</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>Sun, 04 Oct 2026 21:53:03 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-53050</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-53050</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-53050</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0862 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862</link>
      <description>certfr-2026-avi-0862</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862</guid>
    </item>
    <item>
      <title>EUVD-2026-364838</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-364838</link>
      <description>EUVD-2026-364838</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-364838</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53050</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53050</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;quota: Fix race of dquot_scan_active() with quota deactivation&lt;/p&gt;
&lt;p&gt;dquot_scan_active() can race with quota deactivation in
quota_release_workfn() like:&lt;/p&gt;
&lt;p&gt;CPU0 (quota_release_workfn)         CPU1 (dquot_scan_active)
  ==============================      ==============================
  spin_lock(&amp;amp;dq_list_lock);
  list_replace_init(
    &amp;amp;releasing_dquots, &amp;amp;rls_head);
    /* dquot X on rls_head,
       dq_count == 0,
       DQ_ACTIVE_B still set */
  spin_unlock(&amp;amp;dq_list_lock);
  synchronize_srcu(&amp;amp;dquot_srcu);
                                      spin_lock(&amp;amp;dq_list_lock);
                                      list_for_each_entry(dquot,
                                          &amp;amp;inuse_list, dq_inuse) {
                                        /* finds dquot X */
                                        dquot_active(X) -&amp;gt; true
                                        atomic_inc(&amp;amp;X-&amp;gt;dq_count);
                                      }
                                      spin_unlock(&amp;amp;dq_list_lock);
  spin_lock(&amp;amp;dq_list_lock);
  dquot = list_first_entry(&amp;amp;rls_head);
  WARN_ON_ONCE(atomic_read(&amp;amp;dquot-&amp;gt;dq_count));&lt;/p&gt;
&lt;p&gt;The problem is not only a cosmetic one as under memory pressure the
caller of dquot_scan_active() can end up working on freed dquot.&lt;/p&gt;
&lt;p&gt;Fix the problem by making sure the dquot is removed from releasing list
when we acquire a reference to it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;quota: Fix race of dquot_scan_active() with quota deactivation&lt;/p&gt;
&lt;p&gt;dquot_scan_active() can race with quota deactivation in
quota_release_workfn() like:&lt;/p&gt;
&lt;p&gt;CPU0 (quota_release_workfn)         CPU1 (dquot_scan_active)
  ==============================      ==============================
  spin_lock(&amp;amp;dq_list_lock);
  list_replace_init(
    &amp;amp;releasing_dquots, &amp;amp;rls_head);
    /* dquot X on rls_head,
       dq_count == 0,
       DQ_ACTIVE_B still set */
  spin_unlock(&amp;amp;dq_list_lock);
  synchronize_srcu(&amp;amp;dquot_srcu);
                                      spin_lock(&amp;amp;dq_list_lock);
                                      list_for_each_entry(dquot,
                                          &amp;amp;inuse_list, dq_inuse) {
                                        /* finds dquot X */
                                        dquot_active(X) -&amp;gt; true
                                        atomic_inc(&amp;amp;X-&amp;gt;dq_count);
                                      }
                                      spin_unlock(&amp;amp;dq_list_lock);
  spin_lock(&amp;amp;dq_list_lock);
  dquot = list_first_entry(&amp;amp;rls_head);
  WARN_ON_ONCE(atomic_read(&amp;amp;dquot-&amp;gt;dq_count));&lt;/p&gt;
&lt;p&gt;The problem is not only a cosmetic one as under memory pressure the
caller of dquot_scan_active() can end up working on freed dquot.&lt;/p&gt;
&lt;p&gt;Fix the problem by making sure the dquot is removed from releasing list
when we acquire a reference to it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53050</guid>
    </item>
    <item>
      <title>GHSA-4mf5-rjc5-62qc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4mf5-rjc5-62qc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;quota: Fix race of dquot_scan_active() with quota deactivation&lt;/p&gt;
&lt;p&gt;dquot_scan_active() can race with quota deactivation in
quota_release_workfn() like:&lt;/p&gt;
&lt;p&gt;CPU0 (quota_release_workfn)         CPU1 (dquot_scan_active)
  ==============================      ==============================
  spin_lock(&amp;amp;dq_list_lock);
  list_replace_init(
    &amp;amp;releasing_dquots, &amp;amp;rls_head);
    /* dquot X on rls_head,
       dq_count == 0,
       DQ_ACTIVE_B still set */
  spin_unlock(&amp;amp;dq_list_lock);
  synchronize_srcu(&amp;amp;dquot_srcu);
                                      spin_lock(&amp;amp;dq_list_lock);
                                      list_for_each_entry(dquot,
                                          &amp;amp;inuse_list, dq_inuse) {
                                        /* finds dquot X */
                                        dquot_active(X) -&amp;gt; true
                                        atomic_inc(&amp;amp;X-&amp;gt;dq_count);
                                      }
                                      spin_unlock(&amp;amp;dq_list_lock);
  spin_lock(&amp;amp;dq_list_lock);
  dquot = list_first_entry(&amp;amp;rls_head);
  WARN_ON_ONCE(atomic_read(&amp;amp;dquot-&amp;gt;dq_count));&lt;/p&gt;
&lt;p&gt;The problem is not only a cosmetic one as under memory pressure the
caller of dquot_scan_active() can end up working on freed dquot.&lt;/p&gt;
&lt;p&gt;Fix the problem by making sure the dquot is removed from releasing list
when we acquire a reference to it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;quota: Fix race of dquot_scan_active() with quota deactivation&lt;/p&gt;
&lt;p&gt;dquot_scan_active() can race with quota deactivation in
quota_release_workfn() like:&lt;/p&gt;
&lt;p&gt;CPU0 (quota_release_workfn)         CPU1 (dquot_scan_active)
  ==============================      ==============================
  spin_lock(&amp;amp;dq_list_lock);
  list_replace_init(
    &amp;amp;releasing_dquots, &amp;amp;rls_head);
    /* dquot X on rls_head,
       dq_count == 0,
       DQ_ACTIVE_B still set */
  spin_unlock(&amp;amp;dq_list_lock);
  synchronize_srcu(&amp;amp;dquot_srcu);
                                      spin_lock(&amp;amp;dq_list_lock);
                                      list_for_each_entry(dquot,
                                          &amp;amp;inuse_list, dq_inuse) {
                                        /* finds dquot X */
                                        dquot_active(X) -&amp;gt; true
                                        atomic_inc(&amp;amp;X-&amp;gt;dq_count);
                                      }
                                      spin_unlock(&amp;amp;dq_list_lock);
  spin_lock(&amp;amp;dq_list_lock);
  dquot = list_first_entry(&amp;amp;rls_head);
  WARN_ON_ONCE(atomic_read(&amp;amp;dquot-&amp;gt;dq_count));&lt;/p&gt;
&lt;p&gt;The problem is not only a cosmetic one as under memory pressure the
caller of dquot_scan_active() can end up working on freed dquot.&lt;/p&gt;
&lt;p&gt;Fix the problem by making sure the dquot is removed from releasing list
when we acquire a reference to it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4mf5-rjc5-62qc</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-53050 — quota: Fix race of dquot_scan_active() with quota deactivation</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-53050</link>
      <description>msrc_CVE-2026-53050</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-53050</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21388-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21388-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:21388-1</guid>
    </item>
    <item>
      <title>SSA-019113 — SSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6</title>
      <link>https://cve.radiocsirt.org/vuln/ssa-019113</link>
      <description>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ssa-019113</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:22742-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:22742-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:22742-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53050</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53050</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 218 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: quota: Fix race of dquot_scan_active() with quota deactivation dquot_scan_active() can race with quota deactivation in quota_release_workfn() like:   CPU0 (quota_release_workfn)         CPU1 (dquot_scan_active)   ==============================      ==============================   spin_lock(&amp;amp;dq_list_lock);   list_replace_init(     &amp;amp;releasing_dquots, &amp;amp;rls_head);     /* dquot X on rls_head,        dq_count == 0,        DQ_ACTIVE_B still set */   spin_unlock(&amp;amp;dq_list_lock);   synchronize_srcu(&amp;amp;dquot_srcu);                                       spin_lock(&amp;amp;dq_list_lock);                                       list_for_each_entry(dquot,                                           &amp;amp;inuse_list, dq_inuse) {                                         /* finds dquot X */                                         dquot_active(X) -&amp;gt; true                                         atomic_inc(&amp;amp;X-&amp;gt;dq_count);                                       }                                       spin_unlock(&amp;amp;dq_list_lock);   spin_lock(&amp;amp;dq_list_lock);   dquot = list_first_entry(&amp;amp;rls_head);   WARN_ON_ONCE(atomic_read(&amp;amp;dquot-&amp;gt;dq_count)); The problem is not only a cosmetic one as under memory pressure the caller of dquot_scan_active() can end up working on freed dquot. Fix the problem by making sure the dquot is removed from releasing list when we acquire a reference to it.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 218 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: quota: Fix race of dquot_scan_active() with quota deactivation dquot_scan_active() can race with quota deactivation in quota_release_workfn() like:   CPU0 (quota_release_workfn)         CPU1 (dquot_scan_active)   ==============================      ==============================   spin_lock(&amp;amp;dq_list_lock);   list_replace_init(     &amp;amp;releasing_dquots, &amp;amp;rls_head);     /* dquot X on rls_head,        dq_count == 0,        DQ_ACTIVE_B still set */   spin_unlock(&amp;amp;dq_list_lock);   synchronize_srcu(&amp;amp;dquot_srcu);                                       spin_lock(&amp;amp;dq_list_lock);                                       list_for_each_entry(dquot,                                           &amp;amp;inuse_list, dq_inuse) {                                         /* finds dquot X */                                         dquot_active(X) -&amp;gt; true                                         atomic_inc(&amp;amp;X-&amp;gt;dq_count);                                       }                                       spin_unlock(&amp;amp;dq_list_lock);   spin_lock(&amp;amp;dq_list_lock);   dquot = list_first_entry(&amp;amp;rls_head);   WARN_ON_ONCE(atomic_read(&amp;amp;dquot-&amp;gt;dq_count)); The problem is not only a cosmetic one as under memory pressure the caller of dquot_scan_active() can end up working on freed dquot. Fix the problem by making sure the dquot is removed from releasing list when we acquire a reference to it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53050</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2077 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</link>
      <description>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</guid>
    </item>
  </channel>
</rss>
