media: chips-media: wave5: Resume device before setting EOS flag

Summary

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().

Timeline

1. Sep 16, 2026, 10:31 AM UTCCVE published
2. Oct 19, 2026, 8:53 AM UTCRecord last updated

Affected versions

• Linux Linux

  From 9707a6254a8a6b978bde811a44fe07d86c229d1c · fixed in 56c2c5ad35614ca5ae23838d6af5d7f59e3124dc; From 9707a6254a8a6b978bde811a44fe07d86c229d1c · fixed in 2215e55ee1e5e69ad53862d968360c5aa63dd3a7; From 9707a6254a8a6b978bde811a44fe07d86c229d1c · fixed in a52e6f7923c17a672135b485ffd96fbd72f46267

• Linux Linux

  6.8

• KernelLinux

  From 6.8.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.5

References 3