---
id: "CVE-2026-98882"
kind: "vulnerability"
aliases: ["CVE-2026-98882"]
title: "Linux kernel: wave5 media decoder missing range check allows out-of-bounds write"
severity: "unknown"
cvss: null
epss: 0.00223
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["arm-boards", "chips-media-wave5", "embedded", "infrastructure", "linux-kernel"]
not_affected_if: ["driver-not-loaded", "no-wave5-hardware"]
published_at: "2026-10-23T12:18:21+00:00"
first_seen_at: "2026-10-23T21:57:33+00:00"
updated_at: "2026-10-25T12:38:51+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98882", "first_seen_at": "2026-10-23T21:57:33+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-98882", "first_seen_at": "2026-10-25T12:38:51+00:00"}]
---

# Linux kernel: wave5 media decoder missing range check allows out-of-bounds write

The Linux kernel's chips-media wave5 video decoder driver trusts invalid output information from the hardware, which can make it write outside a frame buffer array. The sources describe a kernel memory write, with no stated attacker-controlled path or impact beyond that.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- `uname -r` to see the running kernel version
- `lsmod | grep wave5` to check whether the wave5 driver is loaded
- unknown whether a specific kernel version is fixed; the sources do not list affected or fixed versions

## Fix

- Update the Linux kernel to a release that includes the upstream commit adding range checks in wave5-vpuapi.c; fixed version numbers: unknown
- Check your distribution's kernel advisory for the patched package

## Timeline

- 2026-10-23T21:57:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98882
- 2026-10-25T12:38:51+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-98882

## From the sources

In the Linux kernel, the following vulnerability has been resolved:

media: chips-media: wave5: Add range checks for dec_output_info

If the driver's dec_output_info contains invalid data the driver can
write in invalid memory. Add a range check for that.

This fixes this smatch error:
drivers/media/platform/chips-media/wave5/wave5-vpuapi.c:588 wave5_vpu_dec_get_output_info() error: buffer overflow 'inst->frame_buf' 64 <= 127

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_