No exploitation reportedFix available

CVE-2024-27053

Q: Is CVE-2024-27053 actively exploited?

Active exploitation of CVE-2024-27053 has not been confirmed. Its EPSS score was 1.6% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2024-27053?

CVE-2024-27053 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

No exploitation reported by the sources we read.

Published2024-05-01
Fixed ine556006de4ea · dd50d3ead6e3 · d80fc436751c · b4bbf38c350a · 745003b5917b · 5800ec78775c
WeaknessCWE-476

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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

dates in UTC

2024-05-0113:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-27053?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-27053?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

CISA-ADP · NVD

Linux linux kernel

Branch	Affected	Fixed in	Source
—	≥ c460495ee072, < e556006de4ea	e556006de4ea	CISA-ADP
—	≥ c460495ee072, < dd50d3ead6e3	dd50d3ead6e3	CISA-ADP
—	≥ c460495ee072, < d80fc436751c	d80fc436751c	CISA-ADP
—	≥ c460495ee072, < b4bbf38c350a	b4bbf38c350a	CISA-ADP
745003.x	≥ c460495ee072, < 745003b5917b	745003b5917b	CISA-ADP
5800.x	≥ c460495ee072, < 5800ec78775c	5800ec78775c	CISA-ADP
205.x	≥ c460495ee072, < 205c50306acf	205c50306acf	CISA-ADP
6.8	≥ 6.8, < 6.8.2	6.8.2	NVD
6.7	≥ 6.7, < 6.7.11	6.7.11	NVD
6.x	≥ 6.2, < 6.6.23	6.6.23	NVD
6.1	≥ 5.16, < 6.1.83	6.1.83	NVD
5.x	≥ 5.11, < 5.15.153	5.15.153	NVD

Debian debian linux

Branch	Affected	Fixed in	Source
10.0	= 10.0	no fix published	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Update Linux linux kernel to e556006de4ea · dd50d3ead6e3 · d80fc436751c · b4bbf38c350a · 745003b5917b · 5800ec78775c · 205c50306acf · 6.8.2

Advisories and patches

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVE recordread 2026-10-23
CISA-ADPSSVC decisionnone2025-02-05
OpenCVESSVC decisionnone—
CISA-ADPCVSS 3.19.12024-05-28
CNACVSS 3.18.8read 2026-10-23
CISA-ADPweakness (CWE)CWE-4762024-05-28
FIRST EPSSEPSS score1.6 %2026-10-22

Technical details

CVSS v3 Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published: 2024-05-01
Last Modified: 2026-10-15
NVD status: Modified

Frequently asked questions

What is CVE-2024-27053?

Is CVE-2024-27053 actively exploited?

Active exploitation of CVE-2024-27053 has not been confirmed. Its EPSS score was 1.6% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-27053?

CVE-2024-27053 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database