Live › vulnerability › CVE-2026-98882
Go to dashboardThe 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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the chips-media wave5 video decoder driver, which is used by certain Chips&Media VPU hardware in embedded and ARM boards. Systems without that hardware or without the driver loaded are unlikely to be exposed. The sources do not say how an attacker would reach the driver.
No product ranges from the sources yet.
uname -r to see the running kernel versionlsmod | grep wave5 to check whether the wave5 driver is loadedEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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
This page as .md · .json · in your agent: get_signal("CVE-2026-98882")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.