<?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>Mon, 05 Oct 2026 15:27:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-48985 — net: mana: Fix race on per-CQ variable napi work_done</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-48985</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: mana: Fix race on per-CQ variable napi work_done&lt;/p&gt;
&lt;p&gt;After calling napi_complete_done(), the NAPIF_STATE_SCHED bit may be
cleared, and another CPU can start napi thread and access per-CQ variable,
cq-&amp;gt;work_done. If the other thread (for example, from busy_poll) sets
it to a value &amp;gt;= budget, this thread will continue to run when it should
stop, and cause memory corruption and panic.&lt;/p&gt;
&lt;p&gt;To fix this issue, save the per-CQ work_done variable in a local variable
before napi_complete_done(), so it won&amp;#39;t be corrupted by a possible
concurrent thread after napi_complete_done().&lt;/p&gt;
&lt;p&gt;Also, add a flag bit to advertise to the NIC firmware: the NAPI work_done
variable race is fixed, so the driver is able to reliably support features
like busy_poll.&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: mana: Fix race on per-CQ variable napi work_done&lt;/p&gt;
&lt;p&gt;After calling napi_complete_done(), the NAPIF_STATE_SCHED bit may be
cleared, and another CPU can start napi thread and access per-CQ variable,
cq-&amp;gt;work_done. If the other thread (for example, from busy_poll) sets
it to a value &amp;gt;= budget, this thread will continue to run when it should
stop, and cause memory corruption and panic.&lt;/p&gt;
&lt;p&gt;To fix this issue, save the per-CQ work_done variable in a local variable
before napi_complete_done(), so it won&amp;#39;t be corrupted by a possible
concurrent thread after napi_complete_done().&lt;/p&gt;
&lt;p&gt;Also, add a flag bit to advertise to the NIC firmware: the NAPI work_done
variable race is fixed, so the driver is able to reliably support features
like busy_poll.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-48985</guid>
    </item>
  </channel>
</rss>
