Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97516 Overview
CVE-2026-97516 is a NULL pointer dereference vulnerability in the Linux kernel's rtw88 wireless driver. The flaw resides in the rtw_fw_adaptivity_result() function in fw.c, which dereferences rtwdev->chip->edcca_th without a NULL check. Devices using the Realtek 8821CE chip do not define edcca_th in their chip info structure. When the function attempts to access this field, the kernel generates an oops, resulting in a denial-of-service condition on affected systems. The upstream fix adds a NULL check at the function entry to prevent the dereference while a permanent solution is developed.
Critical Impact
Systems running the Linux kernel with Realtek 8821CE wireless hardware can experience a kernel oops when rtw_fw_adaptivity_result() executes, disrupting wireless connectivity and system stability.
Affected Products
- Linux kernel versions containing the rtw88 wireless driver
- Systems using Realtek 8821CE WiFi chipsets
- Distributions shipping the vulnerable rtw88 driver prior to the referenced stable commits
Discovery Timeline
- 2026-09-24 - CVE-2026-97516 published to the National Vulnerability Database
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-97516
Vulnerability Analysis
The issue is a NULL Pointer Dereference [CWE-476] in the rtw88 driver that supports Realtek 802.11ac wireless chipsets. The rtw_fw_adaptivity_result() function processes adaptivity (EDCCA, Energy Detect Clear Channel Assessment) results reported by the device firmware. The function reads threshold values from rtwdev->chip->edcca_th to interpret the reported data.
The edcca_th field is populated only for a subset of supported chips. The 8821CE chip's rtw_chip_info structure omits the field, leaving the pointer unset. When adaptivity results arrive for an 8821CE device, the function reads from an invalid address and the kernel triggers an oops. The fix adds an early NULL check so the function returns cleanly without logging uninitialized data.
Root Cause
The root cause is a missing precondition check on a chip-dependent optional pointer. The driver was written assuming every supported chip provides edcca_th data, but the 8821CE chip definition does not supply it. The fix is a defensive guard; a permanent solution requires populating the chip info or restructuring adaptivity handling.
Attack Vector
Triggering the oops requires the driver to process an adaptivity result on affected hardware. This path is reached during normal wireless operation on 8821CE devices. The condition is primarily a reliability and availability issue rather than a path to code execution. Local or adjacent attackers who can influence wireless firmware events on vulnerable hardware may be able to repeatedly induce the oops.
No verified public exploit code is available for CVE-2026-97516. See the Kernel Git Commit Fix for the applied patch.
Detection Methods for CVE-2026-97516
Indicators of Compromise
- Kernel oops messages in dmesg or /var/log/kern.log referencing rtw_fw_adaptivity_result or the rtw88 module
- Unexpected wireless interface resets or driver reinitialization events on hosts with Realtek 8821CE chipsets
- Soft lockups or panics correlated with wireless activity on affected hardware
Detection Strategies
- Audit kernel versions on managed Linux endpoints and identify systems running rtw88 builds that predate the stable commits 6fa23cafaf30, 1d1f250432cd, and d5e6f353ce1e.
- Inventory wireless hardware across the fleet and flag devices reporting the Realtek 8821CE PCI ID as higher-priority patch targets.
- Monitor crash telemetry and journald logs for repeated rtw88 oops traces that indicate the condition is being hit.
Monitoring Recommendations
- Forward kernel ring buffer events to a centralized log platform and alert on kernel oops signatures.
- Track wireless driver reload counts over time to surface instability patterns on affected endpoints.
- Correlate hardware inventory with kernel version data to prioritize remediation on hosts carrying 8821CE radios.
How to Mitigate CVE-2026-97516
Immediate Actions Required
- Apply the stable kernel update containing commit 6fa23cafaf30f4877e357f8eebcff00dff4aa9cb or the backports referenced in the NVD entry.
- Prioritize patching on endpoints and embedded systems that use Realtek 8821CE wireless adapters.
- Reboot affected systems after patching so the fixed rtw88 module is loaded.
Patch Information
The Linux kernel maintainers resolved the issue by adding a NULL check for chip->edcca_th at the entry of rtw_fw_adaptivity_result(). Fixes are available in the following stable commits: Kernel Git Commit Fix, Kernel Git Commit Update, and Kernel Git Commit Improvement. Distribution kernels will inherit the fix once rebased onto a stable release containing these commits.
Workarounds
- Unload the rtw88 module (modprobe -r rtw88_8821ce rtw88_pci rtw88_core) on systems where wireless is not required, until a patched kernel is deployed.
- Blacklist the rtw88_8821ce module on affected systems and use an alternative supported adapter where feasible.
- Disable wireless radios in firmware or at the hardware switch on devices that will remain unpatched in production.
# Blacklist the vulnerable driver until the patched kernel is installed
echo "blacklist rtw88_8821ce" | sudo tee /etc/modprobe.d/blacklist-rtw88-8821ce.conf
sudo modprobe -r rtw88_8821ce
sudo update-initramfs -u
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

