Answer in brief
CVE-2026-97516 records a Unknown severity vulnerability in wifi: rtw88: Add NULL check for chip->edcca_th in rtw_fw_adaptivity_result(). The current sources do not mark it as known exploited. The current feed maps 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6fa23cafaf30f4877e357f8eebcff00dff4aa9cb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1d1f250432cd8704c3c125168887f9724021c81a || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d5e6f353ce1e1c25b8458ea390ed09d2377412c5 || >=0 <6.12.111 || >=0 <6.18.53 | 6fa23cafaf30f4877e357f8eebcff00dff4aa9cb, 1d1f250432cd8704c3c125168887f9724021c81a, d5e6f353ce1e1c25b8458ea390ed09d2377412c5, 6.12.111, 6.18.53 |
Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: Add NULL check for chip->edcca_th in rtw_fw_adaptivity_result() It was recently reported that rtw_fw_adaptivity_result() in fw.c dereferences rtwdev->chip->edcca_th without a NULL check. The issue is that devices with the 8821CE chip don't define edcca_th in their chip info. As a result, when rtw_fw_adaptivity_result() tries to dereference it, the kernel triggers an oops. Add a NULL check for edcca_th before dereferencing it in rtw_fw_adaptivity_result() in fw.c. Placing the check at the function entry avoids logging any garbage values. This change does not address the root cause for this behavior, but it prevents the NULL dereference and the resulting oops while a more permanent solution is developed. Tested on a 8822CE chip which defines edcca_th, so this issue is not present on it, but it still uses this driver and I can verify there are no regressions.
Quoted source text, attributed separately from HOL analysis.