In the Linux kernel, the following vulnerability has been resolved:
lan966x: Fix sleeping in atomic context
The following warning was seen when we try to connect using ssh to the device.
BUG: sleeping function called from invalid context at kernel/locking/mutex.c:575 inatomic(): 1, irqsdisabled(): 0, nonblock: 0, pid: 104, name: dropbear preemptcount: 1, expected: 0 INFO: lockdep is turned off. CPU: 0 UID: 0 PID: 104 Comm: dropbear Tainted: G W 6.18.0-rc2-00399-g6f1ab1b109b9-dirty #530 NONE Tainted: [W]=WARN Hardware name: Generic DT based system Call trace: unwindbacktrace from showstack+0x10/0x14 showstack from dumpstacklvl+0x7c/0xac dumpstacklvl from _mightresched+0x16c/0x2b0 _mightresched from _mutexlock+0x64/0xd34 _mutexlock from mutexlocknested+0x1c/0x24 mutexlocknested from lan966xstatsget+0x5c/0x558 lan966xstatsget from devgetstats+0x40/0x43c devgetstats from devseqprintfstats+0x3c/0x184 devseqprintfstats from devseqshow+0x10/0x30 devseqshow from seqreaditer+0x350/0x4ec seqreaditer from seqread+0xfc/0x194 seqread from procregread+0xac/0x100 procregread from vfsread+0xb0/0x2b0 vfsread from ksysread+0x6c/0xec ksysread from retfast_syscall+0x0/0x1c Exception stack(0xf0b11fa8 to 0xf0b11ff0) 1fa0: 00000001 00001000 00000008 be9048d8 00001000 00000001 1fc0: 00000001 00001000 00000008 00000003 be905920 0000001e 00000000 00000001 1fe0: 0005404c be9048c0 00018684 b6ec2cd8
It seems that we are using a mutex in a atomic context which is wrong. Change the mutex with a spinlock.
{
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68320.json"
}