Security readout for executives and security teams
Plain-English summary
A flaw in Linux's wilc1000 Wi-Fi driver can read shared memory after kernel synchronization protection has ended. Under nearby wireless conditions, that stale access could cause crashes, data corruption, or unintended kernel-memory access. Risk is concentrated in devices using this specific driver, not every Linux system.
Executive priority
Treat this as high priority for fleets using wilc1000, especially wirelessly reachable devices. Confirm driver use first, then expedite supported kernel updates. For systems without this driver, document non-exposure rather than triggering a fleet-wide emergency. No active exploitation evidence is supplied.
Technical view
wilc_parse_join_bss_param dereferences ies->tsf after leaving its RCU read-side critical section. The pointer may then reference changed or freed memory, creating a potential use-after-free with confidentiality, integrity, and availability consequences. The published fix copies TSF into a local variable before rcu_read_unlock() and uses that value afterward.
Likely exposure
Exposure is limited to Linux systems whose running kernel includes the vulnerable wilc1000 Wi-Fi code and uses that driver. General Linux systems without this driver are unlikely to be exposed. The supplied version entries contain conflicting affected and unaffected labeling, so map vendor kernels to advisories or cited fix commits.
Exploitation context
The 8.3 CVSS vector describes an unauthenticated, adjacent-network attack requiring no user interaction. However, the bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, a public exploit, or successful real-world attacks. The issue was identified through static analysis.
Researcher notes
The defect is an RCU lifetime violation: ies->tsf is consumed after rcu_read_unlock(). The correction snapshots TSF into ies_tsf while protected and later assigns param->tsf_lo from the local value. The bundle provides no reproducer, observed attack, CWE assignment, or reliably interpretable per-release affected ranges.
Mitigation direction
- Identify systems where the wilc1000 driver is present and actively used.
- Apply supported distribution kernel updates incorporating the upstream wilc1000 correction.
- Consult vendor advisories before relying on the bundle's ambiguous version mapping.
- Follow distribution guidance to activate the corrected kernel after updating.
Validation and detection
- Inventory each system's running kernel release and wilc1000 driver usage.
- Map vendor kernel builds to applicable advisories or cited stable fix commits.
- For custom kernels, verify TSF is copied before the RCU read lock is released.
- After maintenance, confirm the running kernel is the corrected vendor build.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2024-47712 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H2.85.5LinuxVulnerability scoring details
Base CVSS 3.1 score
8.3HighVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/5a24cedc243ace5ed7c1016f52a7bfc8f5b07815CVE reference, Linux
- https://git.kernel.org/stable/c/557418e1704605a81c9e26732449f71b1d40ba1eCVE reference, Linux
- https://git.kernel.org/stable/c/bf090f4fe935294361eabd9dc5a949fdd77d3d1bCVE reference, Linux
- https://git.kernel.org/stable/c/b040b71d99ee5e17bb7a743dc01cbfcae8908ce1CVE reference, Linux
- https://git.kernel.org/stable/c/84398204c5df5aaf89453056cf0647cda9664d2bCVE reference, Linux
- https://git.kernel.org/stable/c/2f944e6255c2fc1c9bd9ee32f6b14ee0b2a51eb5CVE reference, Linux
- https://git.kernel.org/stable/c/79510414a7626317f13cc9073244ab7a8deb3192CVE reference, Linux
- https://git.kernel.org/stable/c/6d7c6ae1efb1ff68bc01d79d94fdf0388f86cdd8CVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/03/msg00002.htmlCVE reference, CVE
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.