CVE-2024-41036: net: ks8851: Fix deadlock with the SPI chip variant
In the Linux kernel, the following vulnerability has been resolved:
net: ks8851: Fix deadlock with the SPI chip variant
When SMP is enabled and spinlocks are actually functional then there is
a deadlock with the 'statelock' spinlock between ks8851_start_xmit_spi
and ks8851_irq:
watchdog: BUG: soft lockup - CPU#0 stuck for 27s!
call trace:
queued_spin_lock_slowpath+0x100/0x284
do_raw_spin_lock+0x34/0x44
ks8851_start_xmit_spi+0x30/0xb8
ks8851_start_xmit+0x14/0x20
netdev_start_xmit+0x40/0x6c
dev_hard_start_xmit+0x6c/0xbc
sch_direct_xmit+0xa4/0x22c
__qdisc_run+0x138/0x3fc
qdisc_run+0x24/0x3c
net_tx_action+0xf8/0x130
handle_softirqs+0x1ac/0x1f0
__do_softirq+0x14/0x20
____do_softirq+0x10/0x1c
call_on_irq_stack+0x3c/0x58
do_softirq_own_stack+0x1c/0x28
__irq_exit_rcu+0x54/0x9c
irq_exit_rcu+0x10/0x1c
el1_interrupt+0x38/0x50
el1h_64_irq_handler+0x18/0x24
el1h_64_irq+0x64/0x68
__netif_schedule+0x6c/0x80
netif_tx_wake_queue+0x38/0x48
ks8851_irq+0xb8/0x2c8
irq_thread_fn+0x2c/0x74
irq_thread+0x10c/0x1b0
kthread+0xc8/0xd8
ret_from_fork+0x10/0x20
This issue has not been identified earlier because tests were done on
a device with SMP disabled and so spinlocks were actually NOPs.
Now use spin_(un)lock_bh for TX queue related locking to avoid execution
of softirq work synchronously that would lead to a deadlock.
Security readout for executives and security teams
Plain-English summary
CVE-2024-41036 is a Linux kernel driver bug that can deadlock systems using the KS8851 SPI Ethernet chip variant on SMP systems. The business impact is availability: affected embedded or appliance-like Linux devices could hang or lose reliable networking. The source bundle does not show active exploitation.
Executive priority
Treat this as a targeted availability risk, highest for Linux-based appliances or embedded systems that rely on KS8851 SPI Ethernet. It does not currently justify emergency enterprise-wide action without matching hardware or kernel exposure.
Technical view
The ks8851 SPI network driver can deadlock on the statelock spinlock between transmit handling and interrupt handling when SMP makes spinlocks functional. The kernel fix changes TX queue locking to spin_lock_bh/spin_unlock_bh to avoid synchronous softirq execution causing the deadlock.
Likely exposure
Exposure is likely limited to Linux systems using the ks8851 SPI Ethernet driver and affected kernel builds. General-purpose Linux servers without that hardware or driver path are less likely exposed. Version evidence is commit and kernel-series based, so distribution backports must be checked directly.
Exploitation context
The bundle reports no KEV listing and provides no evidence of active exploitation. The described failure is a driver deadlock observed through a kernel soft lockup trace, not a publicly documented remote compromise path.
Researcher notes
Focus validation on driver presence, SMP status, and vendor backport status. The CVE record’s affected-version data is not enough to prove exposure for downstream distributions because kernel fixes are often backported without changing the upstream version number.
Mitigation direction
Update to a vendor or distribution kernel containing the CVE-2024-41036 ks8851 fix.
For Debian LTS systems, review and apply the referenced Debian advisory updates.
Prioritize embedded Linux devices using KS8851 SPI Ethernet with SMP enabled.
If patch timing is unclear, ask the kernel or device vendor for fixed-build confirmation.
Validation and detection
Inventory systems for KS8851 SPI Ethernet hardware or loaded ks8851 SPI driver support.
Confirm the running kernel includes one of the referenced stable fixes or a vendor backport.
Review kernel logs for soft lockup traces involving ks8851_start_xmit_spi or ks8851_irq.
After updating, regression test networking under transmit and interrupt load.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-41036 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.