CVE-2024-41036: Linux kernel · net: ks8851: Fix deadlock with the SPI chip variant
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in 6.8.0-1018.19~22.04.1 : patch Linux kernel soon.
Data as of 28 Oct 2026, 11:12 UTC
- Patch
- Available – fixed in 6.8.0-1018.19~22.04.1, 6.8.0-1017.20~22.04.1, 6.8.0-1017.19~22.04.1 +22
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7089-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7090-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7095-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-6 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-7 (opens in a new tab)
- ubuntu.com/security/notices/USN-7156-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkeoppkg:deb/ubuntu/linux-gkeop?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2024-41036 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-41036 (opens in a new tab)
- git.kernel.org/linus/0913ec336a6c0c4a2b296bd9f74f8e41c4c83c8c (opens in a new tab)
- git.kernel.org/stable/c/a0c69c492f4a8fad52f0a97565241c926160c9a4 (opens in a new tab)
- git.kernel.org/stable/c/80ece00137300d74642f2038c8fe5440deaf9f05 (opens in a new tab)
- git.kernel.org/stable/c/10fec0cd0e8f56ff06c46bb24254c7d8f8f2bbf0 (opens in a new tab)
- git.kernel.org/stable/c/0913ec336a6c0c4a2b296bd9f74f8e41c4c83c8c (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7090-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7095-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-6 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-7 (opens in a new tab)
- ubuntu.com/security/notices/USN-7156-1 (opens in a new tab)