<?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 20:49:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90098 — net: sparx5: fix sleep in atomic context in MAC table access</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90098</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: sparx5: fix sleep in atomic context in MAC table access&lt;/p&gt;
&lt;p&gt;sparx5_set_rx_mode() runs with netif_addr_lock_bh held and iterates
dev-&amp;gt;mc via __dev_mc_sync(), which per address calls sparx5_mc_sync() /
sparx5_mc_unsync() -&amp;gt; sparx5_mact_learn() / sparx5_mact_forget().  These
take sparx5-&amp;gt;lock, a mutex, and then poll the MAC access command
register with readx_poll_timeout(). A mutex may block, which is not
allowed from atomic context.&lt;/p&gt;
&lt;p&gt;Convert the driver to the new .ndo_set_rx_mode_async callback introduced
in commit 3554b4345d85 (&amp;#34;net: introduce ndo_set_rx_mode_async and
netdev_rx_mode_work&amp;#34;). The async callback is invoked from process
context, so the mutex and sleeping completion poll can remain.&lt;/p&gt;
&lt;p&gt;Observed with CONFIG_PROVE_LOCKING, CONFIG_DEBUG_SPINLOCK,
CONFIG_DEBUG_MUTEXES and CONFIG_DEBUG_ATOMIC_SLEEP enabled:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/mutex.c:591
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 217, name: ip
  preempt_count: 201, expected: 0
  Call trace:
   __might_resched+0x144/0x248
   __might_sleep+0x48/0x7c
   __mutex_lock+0x74/0x850
   mutex_lock_nested+0x24/0x30
   sparx5_mact_learn+0x78/0x100
   sparx5_mc_sync+0x40/0x54
   __hw_addr_sync_dev+0xc4/0x170
   sparx5_set_rx_mode+0x4c/0x58
   __dev_set_rx_mode+0x64/0xa4
   __dev_open+0x1ec/0x26c&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: sparx5: fix sleep in atomic context in MAC table access&lt;/p&gt;
&lt;p&gt;sparx5_set_rx_mode() runs with netif_addr_lock_bh held and iterates
dev-&amp;gt;mc via __dev_mc_sync(), which per address calls sparx5_mc_sync() /
sparx5_mc_unsync() -&amp;gt; sparx5_mact_learn() / sparx5_mact_forget().  These
take sparx5-&amp;gt;lock, a mutex, and then poll the MAC access command
register with readx_poll_timeout(). A mutex may block, which is not
allowed from atomic context.&lt;/p&gt;
&lt;p&gt;Convert the driver to the new .ndo_set_rx_mode_async callback introduced
in commit 3554b4345d85 (&amp;#34;net: introduce ndo_set_rx_mode_async and
netdev_rx_mode_work&amp;#34;). The async callback is invoked from process
context, so the mutex and sleeping completion poll can remain.&lt;/p&gt;
&lt;p&gt;Observed with CONFIG_PROVE_LOCKING, CONFIG_DEBUG_SPINLOCK,
CONFIG_DEBUG_MUTEXES and CONFIG_DEBUG_ATOMIC_SLEEP enabled:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/mutex.c:591
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 217, name: ip
  preempt_count: 201, expected: 0
  Call trace:
   __might_resched+0x144/0x248
   __might_sleep+0x48/0x7c
   __mutex_lock+0x74/0x850
   mutex_lock_nested+0x24/0x30
   sparx5_mact_learn+0x78/0x100
   sparx5_mc_sync+0x40/0x54
   __hw_addr_sync_dev+0xc4/0x170
   sparx5_set_rx_mode+0x4c/0x58
   __dev_set_rx_mode+0x64/0xa4
   __dev_open+0x1ec/0x26c&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90098</guid>
    </item>
  </channel>
</rss>
