CVE-2024-27053: wifi: wilc1000: fix RCU usage in connect path
In the Linux kernel, the following vulnerability has been resolved:
wifi: wilc1000: fix RCU usage in connect path
With lockdep enabled, calls to the connect function from cfg802.11 layer lead to the following warning:
============================= WARNING: suspicious RCU usage 6.7.0-rc1-wt+ #333 Not tainted ----------------------------- drivers/net/wireless/microchip/wilc1000/hif.c:386 suspicious rcudereferencecheck() usage! [...] stack backtrace: CPU: 0 PID: 100 Comm: wpasupplicant Not tainted 6.7.0-rc1-wt+ #333 Hardware name: Atmel SAMA5 unwindbacktrace from showstack+0x18/0x1c showstack from dumpstacklvl+0x34/0x48 dumpstacklvl from wilcparsejoinbssparam+0x7dc/0x7f4 wilcparsejoinbssparam from connect+0x2c4/0x648 connect from cfg80211connect+0x30c/0xb74 cfg80211connect from nl80211connect+0x860/0xa94 nl80211connect from genlrcvmsg+0x3fc/0x59c genlrcvmsg from netlinkrcvskb+0xd0/0x1f8 netlinkrcvskb from genlrcv+0x2c/0x3c genlrcv from netlinkunicast+0x3b0/0x550 netlinkunicast from netlinksendmsg+0x368/0x688 netlinksendmsg from syssendmsg+0x190/0x430 syssendmsg from syssendmsg+0x110/0x158 syssendmsg from syssendmsg+0xe8/0x150 syssendmsg from retfastsyscall+0x0/0x1c
This warning is emitted because in the connect path, when trying to parse target BSS parameters, we dereference a RCU pointer whithout being in RCU critical section. Fix RCU dereference usage by moving it to a RCU read critical section. To avoid wrapping the whole wilcparsejoinbssparam under the critical section, just use the critical section to copy ies data
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Fixed in 6.7.0-rc1-wt+Patch wifi: wilc1000: fix RCU usage in connect path - Compensating control
If you must run a kernel build that still emits the 'WARNING: suspicious RCU usage' from drivers/net/wireless/microchip/wilc1000/hif.c:386, avoid triggering the cfg80211 nl80211 connect path until the fixed kernel is deployed (the warning occurs when parsing target BSS parameters during connect).
Event History
Frequently Asked Questions
What is the severity of CVE-2024-27053?
CVE-2024-27053 has a high severity rating due to its impact on the Linux kernel's wireless connectivity.
How do I fix CVE-2024-27053?
To fix CVE-2024-27053, upgrade to the fixed versions of the Linux kernel such as 5.10.223-1, 6.1.123-1, or newer releases as specified in the information.
Which Linux kernel versions are affected by CVE-2024-27053?
CVE-2024-27053 affects various versions including 5.10.x and 6.1.x kernels prior to the specified patched versions.
What does CVE-2024-27053 affect in the Linux kernel?
CVE-2024-27053 affects the wifi subsystem, specifically the wilc1000 driver due to incorrect RCU usage in the connect path.
Is CVE-2024-27053 exploitable in production environments?
Yes, CVE-2024-27053 is exploitable in production environments, which necessitates updating to patched kernel versions to mitigate risks.