Answer in brief
CVE-2024-47712 records a Unknown severity vulnerability in wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). 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-47712 records a Unknown severity vulnerability in wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e556006de4ea93abe2b46cba202a2556c544b8b2 <5a24cedc243ace5ed7c1016f52a7bfc8f5b07815 || >=b4bbf38c350acb6500cbe667b1e2e68f896e4b38 <557418e1704605a81c9e26732449f71b1d40ba1e || >=d80fc436751cfa6b02a8eda74eb6cce7dadfe5a2 <bf090f4fe935294361eabd9dc5a949fdd77d3d1b || >=745003b5917b610352f52fe0d11ef658d6471ec2 <b040b71d99ee5e17bb7a743dc01cbfcae8908ce1 || >=4bfd20d5f5c62b5495d6c0016ee6933bd3add7ce <84398204c5df5aaf89453056cf0647cda9664d2b || >=205c50306acf58a335eb19fa84e40140f4fe814f <2f944e6255c2fc1c9bd9ee32f6b14ee0b2a51eb5 || >=205c50306acf58a335eb19fa84e40140f4fe814f <79510414a7626317f13cc9073244ab7a8deb3192 || >=205c50306acf58a335eb19fa84e40140f4fe814f <6d7c6ae1efb1ff68bc01d79d94fdf0388f86cdd8 || 5800ec78775c0cd646f71eb9bf8402fb794807de || dd50d3ead6e3707bb0a5df7cc832730c93ace3a7 || >=5.4.273 <5.4.285 || >=5.10.214 <5.10.227 || >=5.15.153 <5.15.168 || >=6.1.83 <6.1.113 || >=6.6.23 <6.6.54 || >=6.7.11 <6.8 || >=6.8.2 <6.9 | 5a24cedc243ace5ed7c1016f52a7bfc8f5b07815, 557418e1704605a81c9e26732449f71b1d40ba1e, bf090f4fe935294361eabd9dc5a949fdd77d3d1b, b040b71d99ee5e17bb7a743dc01cbfcae8908ce1, 84398204c5df5aaf89453056cf0647cda9664d2b, 2f944e6255c2fc1c9bd9ee32f6b14ee0b2a51eb5, 79510414a7626317f13cc9073244ab7a8deb3192, 6d7c6ae1efb1ff68bc01d79d94fdf0388f86cdd8, 5.4.285, 5.10.227, 5.15.168, 6.1.113, 6.6.54, 6.8, 6.9 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Oct 21, 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 potential RCU dereference issue in wilc_parse_join_bss_param In the `wilc_parse_join_bss_param` function, the TSF field of the `ies` structure is accessed after the RCU read-side critical section is unlocked. According to RCU usage rules, this is illegal. Reusing this pointer can lead to unpredictable behavior, including accessing memory that has been updated or causing use-after-free issues. This possible bug was identified using a static analysis tool developed by myself, specifically designed to detect RCU-related issues. To address this, the TSF value is now stored in a local variable `ies_tsf` before the RCU lock is released. The `param->tsf_lo` field is then assigned using this local variable, ensuring that the TSF value is safely accessed.
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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e556006de4ea93abe2b46cba202a2556c544b8b2 <5a24cedc243ace5ed7c1016f52a7bfc8f5b07815 || >=b4bbf38c350acb6500cbe667b1e2e68f896e4b38 <557418e1704605a81c9e26732449f71b1d40ba1e || >=d80fc436751cfa6b02a8eda74eb6cce7dadfe5a2 <bf090f4fe935294361eabd9dc5a949fdd77d3d1b || >=745003b5917b610352f52fe0d11ef658d6471ec2 <b040b71d99ee5e17bb7a743dc01cbfcae8908ce1 || >=4bfd20d5f5c62b5495d6c0016ee6933bd3add7ce <84398204c5df5aaf89453056cf0647cda9664d2b || >=205c50306acf58a335eb19fa84e40140f4fe814f <2f944e6255c2fc1c9bd9ee32f6b14ee0b2a51eb5 || >=205c50306acf58a335eb19fa84e40140f4fe814f <79510414a7626317f13cc9073244ab7a8deb3192 || >=205c50306acf58a335eb19fa84e40140f4fe814f <6d7c6ae1efb1ff68bc01d79d94fdf0388f86cdd8 || 5800ec78775c0cd646f71eb9bf8402fb794807de || dd50d3ead6e3707bb0a5df7cc832730c93ace3a7 || >=5.4.273 <5.4.285 || >=5.10.214 <5.10.227 || >=5.15.153 <5.15.168 || >=6.1.83 <6.1.113 || >=6.6.23 <6.6.54 || >=6.7.11 <6.8 || >=6.8.2 <6.9 | 5a24cedc243ace5ed7c1016f52a7bfc8f5b07815, 557418e1704605a81c9e26732449f71b1d40ba1e, bf090f4fe935294361eabd9dc5a949fdd77d3d1b, b040b71d99ee5e17bb7a743dc01cbfcae8908ce1, 84398204c5df5aaf89453056cf0647cda9664d2b, 2f944e6255c2fc1c9bd9ee32f6b14ee0b2a51eb5, 79510414a7626317f13cc9073244ab7a8deb3192, 6d7c6ae1efb1ff68bc01d79d94fdf0388f86cdd8, 5.4.285, 5.10.227, 5.15.168, 6.1.113, 6.6.54, 6.8, 6.9 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Oct 21, 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 potential RCU dereference issue in wilc_parse_join_bss_param In the `wilc_parse_join_bss_param` function, the TSF field of the `ies` structure is accessed after the RCU read-side critical section is unlocked. According to RCU usage rules, this is illegal. Reusing this pointer can lead to unpredictable behavior, including accessing memory that has been updated or causing use-after-free issues. This possible bug was identified using a static analysis tool developed by myself, specifically designed to detect RCU-related issues. To address this, the TSF value is now stored in a local variable `ies_tsf` before the RCU lock is released. The `param->tsf_lo` field is then assigned using this local variable, ensuring that the TSF value is safely accessed.
Quoted source text, attributed separately from HOL analysis.