VulnerabilityPublished 19 Jul 2026

CVE-2026-63822: Linux kernel · wifi: ath11k: fix warning when unbinding

Source GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 12:55 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-783h-g799-4r2q

What to do

AI-suggested

A fix has been implemented in the Linux kernel to address this issue by setting buffers to NULL after freeing them, preventing double free. Users should update to the fixed kernel version once available. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the official patch and remediation guidance.

Description

A double free vulnerability was identified and fixed in the Linux kernel's ath11k WiFi driver. The issue occurs when an error during firmware initialization causes certain buffers to be released twice, leading to a warning and potential instability. The fix involves setting the buffers to NULL after release to prevent the double free.

Impact

The vulnerability can cause kernel warnings and potentially memory corruption or instability due to double freeing buffers in the ath11k WiFi driver. This could lead to system crashes or denial of service. There is no indication of remote code execution or privilege escalation from the provided data.

Summary

The Linux kernel's ath11k WiFi driver had a vulnerability where buffers dp->tx_ring[i].tx_status were freed twice if an error occurred during firmware-related initialization. This double free triggered warnings and could cause memory corruption or instability. The problem was reproducible in virtual machines due to MSI addressing initialization failures. The patch sets the buffers to NULL after freeing them to avoid the double free condition.

References

Community reviews

Loading reviews…