<?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>Sat, 03 Oct 2026 12:12:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-57991 — wifi: rtw89: chan: fix soft lockup in rtw89_entity_recalc_mgnt_roles()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-57991</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;wifi: rtw89: chan: fix soft lockup in rtw89_entity_recalc_mgnt_roles()&lt;/p&gt;
&lt;p&gt;During rtw89_entity_recalc_mgnt_roles(), there is a normalizing process
which will re-order the list if an entry with target pattern is found.
And once one is found, should have aborted the list_for_each_entry. But,
`break` just aborted the inner for-loop. The outer list_for_each_entry
still continues. Normally, only the first entry will match the target
pattern, and the re-ordering will change nothing, so there won&amp;#39;t be
soft lockup. However, in some special cases, soft lockup would happen.&lt;/p&gt;
&lt;p&gt;Fix it by `goto fill` to break from the list_for_each_entry.&lt;/p&gt;
&lt;p&gt;The following is a sample of kernel log for this problem.&lt;/p&gt;
&lt;p&gt;watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [wpa_supplicant:2055]
[...]
RIP: 0010:rtw89_entity_recalc ([...] chan.c:392 chan.c:479) rtw89_core
[...]&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;wifi: rtw89: chan: fix soft lockup in rtw89_entity_recalc_mgnt_roles()&lt;/p&gt;
&lt;p&gt;During rtw89_entity_recalc_mgnt_roles(), there is a normalizing process
which will re-order the list if an entry with target pattern is found.
And once one is found, should have aborted the list_for_each_entry. But,
`break` just aborted the inner for-loop. The outer list_for_each_entry
still continues. Normally, only the first entry will match the target
pattern, and the re-ordering will change nothing, so there won&amp;#39;t be
soft lockup. However, in some special cases, soft lockup would happen.&lt;/p&gt;
&lt;p&gt;Fix it by `goto fill` to break from the list_for_each_entry.&lt;/p&gt;
&lt;p&gt;The following is a sample of kernel log for this problem.&lt;/p&gt;
&lt;p&gt;watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [wpa_supplicant:2055]
[...]
RIP: 0010:rtw89_entity_recalc ([...] chan.c:392 chan.c:479) rtw89_core
[...]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-57991</guid>
    </item>
  </channel>
</rss>
