media: amphion: Fix race between m2m job_abort and device_run
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3cd084519c6f91cbef9d604bcf26844fa81d4922 · < 8cd35ceadcfc8c5da2eb7f7ce24525ce9d4ee62e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
media: amphion: Fix race between m2m job_abort and device_run
Fix kernel panic caused by race condition where v4l2_m2m_ctx_release() frees m2m_ctx while v4l2_m2m_try_run() is about to call device_run with the same context.
Race sequence: v4l2_m2m_try_run(): v4l2_m2m_ctx_release(): lock/unlock v4l2_m2m_cancel_job() job_abort() v4l2_m2m_job_finish() kfree(m2m_ctx) <- frees ctx device_run() <- use-after-free crash at 0x538
Crash trace: Unable to handle kernel read from unreadable memory at virtual address 0000000000000538 v4l2_m2m_try_run+0x78/0x138 v4l2_m2m_device_run_work+0x14/0x20
The amphion vpu driver does not rely on the m2m framework's device_run callback to perform encode/decode operations.
Fix the race by preventing m2m framework job scheduling entirely: - Add job_ready callback returning 0 (no jobs ready for m2m framework) - Remove job_abort callback to avoid the race condition
From the CVE record · Linux
A race in the Linux kernel’s amphion VPU driver can free a media context just before the media framework uses it. This can cause a use-after-free and kernel panic; the input does not specify the access or authentication needed to trigger it.
Engineers running Linux kernels with the amphion VPU driver should check their affected versions; no version range is provided.