Answer in brief
CVE-2026-89866 records a Unknown severity vulnerability in media: chips-media: wave5: Resume device before setting EOS flag. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9707a6254a8a6b978bde811a44fe07d86c229d1c <2215e55ee1e5e69ad53862d968360c5aa63dd3a7 || >=9707a6254a8a6b978bde811a44fe07d86c229d1c <a52e6f7923c17a672135b485ffd96fbd72f46267 | 2215e55ee1e5e69ad53862d968360c5aa63dd3a7, a52e6f7923c17a672135b485ffd96fbd72f46267 |
| Linux/Linuxgeneric | 6.8 | Not reported |
| Linux/Linuxgeneric | >=9707a6254a8a6b978bde811a44fe07d86c229d1c <56c2c5ad35614ca5ae23838d6af5d7f59e3124dc || >=9707a6254a8a6b978bde811a44fe07d86c229d1c <2215e55ee1e5e69ad53862d968360c5aa63dd3a7 || >=9707a6254a8a6b978bde811a44fe07d86c229d1c <a52e6f7923c17a672135b485ffd96fbd72f46267 | 56c2c5ad35614ca5ae23838d6af5d7f59e3124dc, 2215e55ee1e5e69ad53862d968360c5aa63dd3a7, a52e6f7923c17a672135b485ffd96fbd72f46267 |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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().
Quoted source text, attributed separately from HOL analysis.