VulnerabilityPublished 16 Sep 2026Updated 10 Nov 2026

CVE-2026-89866: Linux kernel · media: chips-media: wave5: Resume device before setting EOS flag

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in a52e6f7923c17a672135b485ffd96fbd72f46267 : update Linux kernel when convenient.

Data as of 10 Nov 2026, 18:19 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in a52e6f7923c17a672135b485ffd96fbd72f46267, 2215e55ee1e5e69ad53862d968360c5aa63dd3a7, 56c2c5ad35614ca5ae23838d6af5d7f59e3124dc +1

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 10 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

What to do

Upgrade Linux kernel to a52e6f7923c17a672135b485ffd96fbd72f46267, 2215e55ee1e5e69ad53862d968360c5aa63dd3a7, 56c2c5ad35614ca5ae23838d6af5d7f59e3124dc or 9c757d77a6eb58ca4a47cada5ab60451e6c2d247.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 9707a6254a8a6b978bde811a44fe07d86c229d1c, < a52e6f7923c17a672135b485ffd96fbd72f46267	Fixed in a52e6f7923c17a672135b485ffd96fbd72f46267
LinuxLinux	Affected ≥ 9707a6254a8a6b978bde811a44fe07d86c229d1c, < 2215e55ee1e5e69ad53862d968360c5aa63dd3a7	Fixed in 2215e55ee1e5e69ad53862d968360c5aa63dd3a7
LinuxLinux	Affected ≥ 9707a6254a8a6b978bde811a44fe07d86c229d1c, < 56c2c5ad35614ca5ae23838d6af5d7f59e3124dc	Fixed in 56c2c5ad35614ca5ae23838d6af5d7f59e3124dc
LinuxLinux	Affected ≥ 9707a6254a8a6b978bde811a44fe07d86c229d1c, < 9c757d77a6eb58ca4a47cada5ab60451e6c2d247	Fixed in 9c757d77a6eb58ca4a47cada5ab60451e6c2d247
LinuxLinux	Affected =6.8	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Resume device before setting EOS flag Setting the EOS flag talks to the firmware via send_firmware_command(), which accesses VPU registers. Both the STREAMOFF path (wave5_vpu_dec_job_abort()) and the V4L2_DEC_CMD_STOP path (wave5_vpu_dec_stop()) can run while the device is runtime suspended, so those register accesses hit powered-down hardware and the SoC raises an asynchronous SError, panicking the kernel: SError Interrupt on CPU3, code 0x00000000bf000000 -- SError send_firmware_command+0x2c/0x160 [wave5] wave5_vpu_dec_set_bitstream_flag+0x6c/0x80 [wave5] wave5_vpu_dec_update_bitstream_buffer+0x80/0xec [wave5] wave5_vpu_dec_job_abort+0x44/0xa0 [wave5] v4l2_m2m_cancel_job+0x110/0x19c [v4l2_mem2mem] v4l2_m2m_streamoff+0x24/0x140 [v4l2_mem2mem] Resume the device with pm_runtime_resume_and_get() around the EOS firmware command and release it with pm_runtime_put_autosuspend(), matching the runtime PM handling already done in wave5_vpu_dec_device_run().

References

Community reviews

Loading reviews…