Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-97516wifi: rtw88: Add NULL check for chip->edcca_th in rtw_fw_adaptivity_result()

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 9 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected fe7bc23a8c5eba8a49061c1d15d0a9d45ef18130 – < a8cdb18ef80d67790d8611ba94ae3d81901c9e04
    • affected fe7bc23a8c5eba8a49061c1d15d0a9d45ef18130 – < 0b58a5ac9170a6f5e6425f8e1a4b3e1d9c2bf53d
    • affected fe7bc23a8c5eba8a49061c1d15d0a9d45ef18130 – < 6fa23cafaf30f4877e357f8eebcff00dff4aa9cb
    • affected fe7bc23a8c5eba8a49061c1d15d0a9d45ef18130 – < 1d1f250432cd8704c3c125168887f9724021c81a
    • affected fe7bc23a8c5eba8a49061c1d15d0a9d45ef18130 – < d5e6f353ce1e1c25b8458ea390ed09d2377412c5
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97516 badge
[![CVE-2026-97516](https://cveledger.app/badge/CVE-2026-97516.svg)](https://cveledger.app/cve/CVE-2026-97516)

Record last updated .