Answer in brief
CVE-2024-27053 records a Unknown severity vulnerability in wifi: wilc1000: fix RCU usage in connect path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-27053 records a Unknown severity vulnerability in wifi: wilc1000: fix RCU usage in connect path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c460495ee072fc01a9b1e8d72c179510418cafac <e556006de4ea93abe2b46cba202a2556c544b8b2 || >=c460495ee072fc01a9b1e8d72c179510418cafac <b4bbf38c350acb6500cbe667b1e2e68f896e4b38 || >=c460495ee072fc01a9b1e8d72c179510418cafac <d80fc436751cfa6b02a8eda74eb6cce7dadfe5a2 || >=c460495ee072fc01a9b1e8d72c179510418cafac <745003b5917b610352f52fe0d11ef658d6471ec2 || >=c460495ee072fc01a9b1e8d72c179510418cafac <4bfd20d5f5c62b5495d6c0016ee6933bd3add7ce || >=c460495ee072fc01a9b1e8d72c179510418cafac <5800ec78775c0cd646f71eb9bf8402fb794807de || >=c460495ee072fc01a9b1e8d72c179510418cafac <dd50d3ead6e3707bb0a5df7cc832730c93ace3a7 || >=c460495ee072fc01a9b1e8d72c179510418cafac <205c50306acf58a335eb19fa84e40140f4fe814f | e556006de4ea93abe2b46cba202a2556c544b8b2, b4bbf38c350acb6500cbe667b1e2e68f896e4b38, d80fc436751cfa6b02a8eda74eb6cce7dadfe5a2, 745003b5917b610352f52fe0d11ef658d6471ec2, 4bfd20d5f5c62b5495d6c0016ee6933bd3add7ce, 5800ec78775c0cd646f71eb9bf8402fb794807de, dd50d3ead6e3707bb0a5df7cc832730c93ace3a7, 205c50306acf58a335eb19fa84e40140f4fe814f |
| Linux/Linuxgeneric | 5.1 | Not reported |
| linux/linux_kernelgeneric | >=c460495ee072 <e556006de4ea | e556006de4ea |
| linux/linux_kernelgeneric | >=c460495ee072 <b4bbf38c350a | b4bbf38c350a |
| linux/linux_kernelgeneric | >=c460495ee072 <d80fc436751c | d80fc436751c |
| linux/linux_kernelgeneric | >=c460495ee072 <745003b5917b | 745003b5917b |
| linux/linux_kernelgeneric | >=c460495ee072 <4bfd20d5f5c | 4bfd20d5f5c |
| linux/linux_kernelgeneric | >=c460495ee072 <5800ec78775c | 5800ec78775c |
| linux/linux_kernelgeneric | >=c460495ee072 <dd50d3ead6e3 | dd50d3ead6e3 |
| linux/linux_kernelgeneric | >=c460495ee072 <205c50306acf | 205c50306acf |
| linux/linux_kernelgeneric | 5.1 | Not reported |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <* | * |
Published upstream
May 1, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c460495ee072fc01a9b1e8d72c179510418cafac <e556006de4ea93abe2b46cba202a2556c544b8b2 || >=c460495ee072fc01a9b1e8d72c179510418cafac <b4bbf38c350acb6500cbe667b1e2e68f896e4b38 || >=c460495ee072fc01a9b1e8d72c179510418cafac <d80fc436751cfa6b02a8eda74eb6cce7dadfe5a2 || >=c460495ee072fc01a9b1e8d72c179510418cafac <745003b5917b610352f52fe0d11ef658d6471ec2 || >=c460495ee072fc01a9b1e8d72c179510418cafac <4bfd20d5f5c62b5495d6c0016ee6933bd3add7ce || >=c460495ee072fc01a9b1e8d72c179510418cafac <5800ec78775c0cd646f71eb9bf8402fb794807de || >=c460495ee072fc01a9b1e8d72c179510418cafac <dd50d3ead6e3707bb0a5df7cc832730c93ace3a7 || >=c460495ee072fc01a9b1e8d72c179510418cafac <205c50306acf58a335eb19fa84e40140f4fe814f | e556006de4ea93abe2b46cba202a2556c544b8b2, b4bbf38c350acb6500cbe667b1e2e68f896e4b38, d80fc436751cfa6b02a8eda74eb6cce7dadfe5a2, 745003b5917b610352f52fe0d11ef658d6471ec2, 4bfd20d5f5c62b5495d6c0016ee6933bd3add7ce, 5800ec78775c0cd646f71eb9bf8402fb794807de, dd50d3ead6e3707bb0a5df7cc832730c93ace3a7, 205c50306acf58a335eb19fa84e40140f4fe814f |
| Linux/Linuxgeneric | 5.1 | Not reported |
| linux/linux_kernelgeneric | >=c460495ee072 <e556006de4ea | e556006de4ea |
| linux/linux_kernelgeneric | >=c460495ee072 <b4bbf38c350a | b4bbf38c350a |
| linux/linux_kernelgeneric | >=c460495ee072 <d80fc436751c | d80fc436751c |
| linux/linux_kernelgeneric | >=c460495ee072 <745003b5917b | 745003b5917b |
| linux/linux_kernelgeneric | >=c460495ee072 <4bfd20d5f5c | 4bfd20d5f5c |
| linux/linux_kernelgeneric | >=c460495ee072 <5800ec78775c | 5800ec78775c |
| linux/linux_kernelgeneric | >=c460495ee072 <dd50d3ead6e3 | dd50d3ead6e3 |
| linux/linux_kernelgeneric | >=c460495ee072 <205c50306acf | 205c50306acf |
| linux/linux_kernelgeneric | 5.1 | Not reported |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <* | * |
Published upstream
May 1, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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
Quoted source text, attributed separately from HOL analysis.