<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 11:35:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68332 — net: airoha: Fix potential use-after-free in airoha_ppe_deinit()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68332</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;net: airoha: Fix potential use-after-free in airoha_ppe_deinit()&lt;/p&gt;
&lt;p&gt;airoha_ppe_deinit() replaces the NPU pointer with NULL via
rcu_replace_pointer() but does not wait for existing RCU readers
to exit before calling ppe_deinit() and airoha_npu_put(). This can
cause a use-after-free if a reader in an RCU read-side critical
section still holds a reference to the NPU when it is freed.&lt;/p&gt;
&lt;p&gt;The init path (airoha_ppe_init) already calls synchronize_rcu()
after rcu_assign_pointer(), but the deinit path introduced in
commit 6abcf751bc08 (&amp;#34;net: airoha: Fix schedule while atomic in
airoha_ppe_deinit()&amp;#34;) omitted the matching barrier when switching
from rcu_read_lock()/rcu_dereference() to rcu_replace_pointer().&lt;/p&gt;
&lt;p&gt;Add synchronize_rcu() before ppe_deinit() to ensure all existing
RCU readers have completed before the NPU resources are released.&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;net: airoha: Fix potential use-after-free in airoha_ppe_deinit()&lt;/p&gt;
&lt;p&gt;airoha_ppe_deinit() replaces the NPU pointer with NULL via
rcu_replace_pointer() but does not wait for existing RCU readers
to exit before calling ppe_deinit() and airoha_npu_put(). This can
cause a use-after-free if a reader in an RCU read-side critical
section still holds a reference to the NPU when it is freed.&lt;/p&gt;
&lt;p&gt;The init path (airoha_ppe_init) already calls synchronize_rcu()
after rcu_assign_pointer(), but the deinit path introduced in
commit 6abcf751bc08 (&amp;#34;net: airoha: Fix schedule while atomic in
airoha_ppe_deinit()&amp;#34;) omitted the matching barrier when switching
from rcu_read_lock()/rcu_dereference() to rcu_replace_pointer().&lt;/p&gt;
&lt;p&gt;Add synchronize_rcu() before ppe_deinit() to ensure all existing
RCU readers have completed before the NPU resources are released.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68332</guid>
    </item>
  </channel>
</rss>
