<?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://db.gcve.eu</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>Wed, 30 Sep 2026 20:07:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93069 — OPP: Fix cleanup ordering</title>
      <link>https://db.gcve.eu/vuln/cve-2026-93069</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;OPP: Fix cleanup ordering&lt;/p&gt;
&lt;p&gt;Commit 173e02d67494 (&amp;#34;OPP: Initialize scope-based pointers inline&amp;#34;)
added initialization for all pointers. In some cases, the ordering was
changed so that *opp_table was initialized after *opp. This also changes
the order of the registered cleanup functions.&lt;/p&gt;
&lt;p&gt;When the cleanup happens, this can cause use-after-free errors when the
last reference is released and the release function _opp_kref_release
tries to access the already freed opp-&amp;gt;opp_table.&lt;/p&gt;
&lt;p&gt;Initialize *opp_table before *opp again to fix this and ensure the
correct cleanup order.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;OPP: Fix cleanup ordering&lt;/p&gt;
&lt;p&gt;Commit 173e02d67494 (&amp;#34;OPP: Initialize scope-based pointers inline&amp;#34;)
added initialization for all pointers. In some cases, the ordering was
changed so that *opp_table was initialized after *opp. This also changes
the order of the registered cleanup functions.&lt;/p&gt;
&lt;p&gt;When the cleanup happens, this can cause use-after-free errors when the
last reference is released and the release function _opp_kref_release
tries to access the already freed opp-&amp;gt;opp_table.&lt;/p&gt;
&lt;p&gt;Initialize *opp_table before *opp again to fix this and ensure the
correct cleanup order.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-93069</guid>
    </item>
  </channel>
</rss>
