<?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>Sat, 03 Oct 2026 15:01:26 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74405</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74405</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-74405</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1203 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Elles permettent à un attaquant de provoq…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1203</link>
      <description>certfr-2026-avi-1203</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1203</guid>
    </item>
    <item>
      <title>EUVD-2026-354213</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354213</link>
      <description>EUVD-2026-354213</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354213</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74405</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74405</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;OPP: Fix race between OPP addition and lookup&lt;/p&gt;
&lt;p&gt;A race exists between dev_pm_opp_add_dynamic() and
dev_pm_opp_find_freq_exact():&lt;/p&gt;
&lt;p&gt;CPU0 (add)                          CPU1 (lookup)
  -------------------------------     ------------------------------
  _opp_add()
    mutex_lock()
    list_add(&amp;amp;new_opp-&amp;gt;node, head)
    mutex_unlock()                    _opp_table_find_key()
                                        mutex_lock()
                                        dev_pm_opp_get(opp)
                                          kref_get()
                                        mutex_unlock()
    kref_init(&amp;amp;new_opp-&amp;gt;kref)
                                      dev_pm_opp_put()
                                        kref_put_mutex()&lt;/p&gt;
&lt;p&gt;The newly added OPP is inserted into the list before its kref is
initialized. A concurrent lookup can find this OPP and increment its
reference count while it is still uninitialized, leading to refcount
corruption and a potential premature free.&lt;/p&gt;
&lt;p&gt;Fix this by initializing -&amp;gt;kref and -&amp;gt;opp_table before making the OPP
visible via list_add(). This ensures any concurrent lookup observes a
fully initialized object.&lt;/p&gt;
&lt;p&gt;[ Viresh: Updated commit log ]&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;OPP: Fix race between OPP addition and lookup&lt;/p&gt;
&lt;p&gt;A race exists between dev_pm_opp_add_dynamic() and
dev_pm_opp_find_freq_exact():&lt;/p&gt;
&lt;p&gt;CPU0 (add)                          CPU1 (lookup)
  -------------------------------     ------------------------------
  _opp_add()
    mutex_lock()
    list_add(&amp;amp;new_opp-&amp;gt;node, head)
    mutex_unlock()                    _opp_table_find_key()
                                        mutex_lock()
                                        dev_pm_opp_get(opp)
                                          kref_get()
                                        mutex_unlock()
    kref_init(&amp;amp;new_opp-&amp;gt;kref)
                                      dev_pm_opp_put()
                                        kref_put_mutex()&lt;/p&gt;
&lt;p&gt;The newly added OPP is inserted into the list before its kref is
initialized. A concurrent lookup can find this OPP and increment its
reference count while it is still uninitialized, leading to refcount
corruption and a potential premature free.&lt;/p&gt;
&lt;p&gt;Fix this by initializing -&amp;gt;kref and -&amp;gt;opp_table before making the OPP
visible via list_add(). This ensures any concurrent lookup observes a
fully initialized object.&lt;/p&gt;
&lt;p&gt;[ Viresh: Updated commit log ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-74405</guid>
    </item>
    <item>
      <title>GHSA-5fpw-5c2c-j4pp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5fpw-5c2c-j4pp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;OPP: Fix race between OPP addition and lookup&lt;/p&gt;
&lt;p&gt;A race exists between dev_pm_opp_add_dynamic() and
dev_pm_opp_find_freq_exact():&lt;/p&gt;
&lt;p&gt;CPU0 (add)                          CPU1 (lookup)
  -------------------------------     ------------------------------
  _opp_add()
    mutex_lock()
    list_add(&amp;amp;new_opp-&amp;gt;node, head)
    mutex_unlock()                    _opp_table_find_key()
                                        mutex_lock()
                                        dev_pm_opp_get(opp)
                                          kref_get()
                                        mutex_unlock()
    kref_init(&amp;amp;new_opp-&amp;gt;kref)
                                      dev_pm_opp_put()
                                        kref_put_mutex()&lt;/p&gt;
&lt;p&gt;The newly added OPP is inserted into the list before its kref is
initialized. A concurrent lookup can find this OPP and increment its
reference count while it is still uninitialized, leading to refcount
corruption and a potential premature free.&lt;/p&gt;
&lt;p&gt;Fix this by initializing -&amp;gt;kref and -&amp;gt;opp_table before making the OPP
visible via list_add(). This ensures any concurrent lookup observes a
fully initialized object.&lt;/p&gt;
&lt;p&gt;[ Viresh: Updated commit log ]&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;OPP: Fix race between OPP addition and lookup&lt;/p&gt;
&lt;p&gt;A race exists between dev_pm_opp_add_dynamic() and
dev_pm_opp_find_freq_exact():&lt;/p&gt;
&lt;p&gt;CPU0 (add)                          CPU1 (lookup)
  -------------------------------     ------------------------------
  _opp_add()
    mutex_lock()
    list_add(&amp;amp;new_opp-&amp;gt;node, head)
    mutex_unlock()                    _opp_table_find_key()
                                        mutex_lock()
                                        dev_pm_opp_get(opp)
                                          kref_get()
                                        mutex_unlock()
    kref_init(&amp;amp;new_opp-&amp;gt;kref)
                                      dev_pm_opp_put()
                                        kref_put_mutex()&lt;/p&gt;
&lt;p&gt;The newly added OPP is inserted into the list before its kref is
initialized. A concurrent lookup can find this OPP and increment its
reference count while it is still uninitialized, leading to refcount
corruption and a potential premature free.&lt;/p&gt;
&lt;p&gt;Fix this by initializing -&amp;gt;kref and -&amp;gt;opp_table before making the OPP
visible via list_add(). This ensures any concurrent lookup observes a
fully initialized object.&lt;/p&gt;
&lt;p&gt;[ Viresh: Updated commit log ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5fpw-5c2c-j4pp</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-74405 — OPP: Fix race between OPP addition and lookup</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-74405</link>
      <description>msrc_CVE-2026-74405</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-74405</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74405</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74405</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: OPP: Fix race between OPP addition and lookup A race exists between dev_pm_opp_add_dynamic() and dev_pm_opp_find_freq_exact():   CPU0 (add)                          CPU1 (lookup)   -------------------------------     ------------------------------   _opp_add()     mutex_lock()     list_add(&amp;amp;new_opp-&amp;gt;node, head)     mutex_unlock()                    _opp_table_find_key()                                         mutex_lock()                                         dev_pm_opp_get(opp)                                           kref_get()                                         mutex_unlock()     kref_init(&amp;amp;new_opp-&amp;gt;kref)                                       dev_pm_opp_put()                                         kref_put_mutex() The newly added OPP is inserted into the list before its kref is initialized. A concurrent lookup can find this OPP and increment its reference count while it is still uninitialized, leading to refcount corruption and a potential premature free. Fix this by initializing -&amp;gt;kref and -&amp;gt;opp_table before making the OPP visible via list_add(). This ensures any concurrent lookup observes a fully initialized object. [ Viresh: Updated commit log ]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: OPP: Fix race between OPP addition and lookup A race exists between dev_pm_opp_add_dynamic() and dev_pm_opp_find_freq_exact():   CPU0 (add)                          CPU1 (lookup)   -------------------------------     ------------------------------   _opp_add()     mutex_lock()     list_add(&amp;amp;new_opp-&amp;gt;node, head)     mutex_unlock()                    _opp_table_find_key()                                         mutex_lock()                                         dev_pm_opp_get(opp)                                           kref_get()                                         mutex_unlock()     kref_init(&amp;amp;new_opp-&amp;gt;kref)                                       dev_pm_opp_put()                                         kref_put_mutex() The newly added OPP is inserted into the list before its kref is initialized. A concurrent lookup can find this OPP and increment its reference count while it is still uninitialized, leading to refcount corruption and a potential premature free. Fix this by initializing -&amp;gt;kref and -&amp;gt;opp_table before making the OPP visible via list_add(). This ensures any concurrent lookup observes a fully initialized object. [ Viresh: Updated commit log ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74405</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
