CVE-2026-98882: Linux kernel · media: chips-media: wave5: Add range checks for dec_output_info
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d6f777d11c7b34549cdadd8578d4b85f685eb976 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:00 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d6f777d11c7b34549cdadd8578d4b85f685eb976, 144f24ec0fc1e51673611912a6d14ded0a61db43, 79aef69bb0903616f4867f0168aea717a11c439c
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 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.
What to do
Upgrade Linux kernel to d6f777d11c7b34549cdadd8578d4b85f685eb976, 144f24ec0fc1e51673611912a6d14ded0a61db43 or 79aef69bb0903616f4867f0168aea717a11c439c.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel commits identified by hashes d6f777d11c7b34549cdadd8578d4b85f685eb976, 144f24ec0fc1e51673611912a6d14ded0a61db43, and 79aef69bb0903616f4867f0168aea717a11c439c. Users should update to the fixed kernel version or apply these patches to mitigate the vulnerability.
Description
A vulnerability in the Linux kernel's chips-media wave5 driver allowed invalid data in dec_output_info to cause out-of-bounds memory writes. This was fixed by adding range checks to prevent buffer overflow in the driver's frame buffer handling.