Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2024-27053

wifi: wilc1000: fix RCU usage in connect path

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.4.273, 5.10.214, 5.15.153, 6.1.83, 6.6.23, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

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 rcu_dereference_check() usage! [...] stack backtrace: CPU: 0 PID: 100 Comm: wpa_supplicant Not tainted 6.7.0-rc1-wt+ #333 Hardware name: Atmel SAMA5 unwind_backtrace from show_stack+0x18/0x1c show_stack from dump_stack_lvl+0x34/0x48 dump_stack_lvl from wilc_parse_join_bss_param+0x7dc/0x7f4 wilc_parse_join_bss_param from connect+0x2c4/0x648 connect from cfg80211_connect+0x30c/0xb74 cfg80211_connect from nl80211_connect+0x860/0xa94 nl80211_connect from genl_rcv_msg+0x3fc/0x59c genl_rcv_msg from netlink_rcv_skb+0xd0/0x1f8 netlink_rcv_skb from genl_rcv+0x2c/0x3c genl_rcv from netlink_unicast+0x3b0/0x550 netlink_unicast from netlink_sendmsg+0x368/0x688 netlink_sendmsg from ____sys_sendmsg+0x190/0x430 ____sys_sendmsg from ___sys_sendmsg+0x110/0x158 ___sys_sendmsg from sys_sendmsg+0xe8/0x150 sys_sendmsg from ret_fast_syscall+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 wilc_parse_join_bss_param under the critical section, just use the critical section to copy ies data

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  3. Record last updated

Affected versions

  • Linux Linux

    From c460495ee072fc01a9b1e8d72c179510418cafac · fixed in e556006de4ea93abe2b46cba202a2556c544b8b2; From c460495ee072fc01a9b1e8d72c179510418cafac · fixed in b4bbf38c350acb6500cbe667b1e2e68f896e4b38; From c460495ee072fc01a9b1e8d72c179510418cafac · fixed in d80fc436751cfa6b02a8eda74eb6cce7dadfe5a2; From c460495ee072fc01a9b1e8d72c179510418cafac · fixed in 745003b5917b610352f52fe0d11ef658d6471ec2; From c460495ee072fc01a9b1e8d72c179510418cafac · fixed in 4bfd20d5f5c62b5495d6c0016ee6933bd3add7ce; From c460495ee072fc01a9b1e8d72c179510418cafac · fixed in 5800ec78775c0cd646f71eb9bf8402fb794807de; From c460495ee072fc01a9b1e8d72c179510418cafac · fixed in dd50d3ead6e3707bb0a5df7cc832730c93ace3a7; From c460495ee072fc01a9b1e8d72c179510418cafac · fixed in 205c50306acf58a335eb19fa84e40140f4fe814f

  • Linux Linux

    5.1

  • KernelLinux

    From 5.1.0 · fixed in 5.4.273; From 5.5.0 · fixed in 5.10.214; From 5.11.0 · fixed in 5.15.153; From 5.16.0 · fixed in 6.1.83; From 6.2.0 · fixed in 6.6.23; From 6.7.0 · fixed in 6.7.11; From 6.8.0 · fixed in 6.8.2

References 8

git.kernel.org