Description
In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Use spinlock for context list protection lock Previously a mutex was added to protect the encoder and decoder context lists from unexpected changes originating from the SCP IP block, causing the context pointer to go invalid, resulting in a NULL pointer dereference in the IPI handler. Turns out on the MT8173, the VPU IPI handler is called from hard IRQ context. This causes a big warning from the scheduler. This was first reported downstream on the ChromeOS kernels, but is also reproducible on mainline using Fluster with the FFmpeg v4l2m2m decoders. Even though the actual capture format is not supported, the affected code paths are triggered. Since this lock just protects the context list and operations on it are very fast, it should be OK to switch to a spinlock.
Product status
0a2dc707aa42214f9c4827bd57e344e29a0841d6 (git) before 2c1ea6214827041f548279c9eda341eda0cc8351
6467cda18c9f9b5f2f9a0aa1e2861c653e41f382 (git) before b92c19675f632a41af1222027a231bc2b7efa7ed
6467cda18c9f9b5f2f9a0aa1e2861c653e41f382 (git) before 3e858938b0e659f6ec9ddcf853a87f1c5c3f44e1
6467cda18c9f9b5f2f9a0aa1e2861c653e41f382 (git) before a5844227e0f030d2af2d85d4aed10c5eca6ca176
23aaf824121055ba81b55f75444355bd83c8eb38 (git)
41671f0c0182b2bae74ca7e3b0f155559e3e2fc5 (git)
51c84a8aac6e3b59af2b0e92ba63cabe2e641a2d (git)
6.9
Any version before 6.9
6.6.120 (semver)
6.12.64 (semver)
6.18.4 (semver)
6.19 (original_commit_for_fix)
References
git.kernel.org/...c/2c1ea6214827041f548279c9eda341eda0cc8351
git.kernel.org/...c/b92c19675f632a41af1222027a231bc2b7efa7ed
git.kernel.org/...c/3e858938b0e659f6ec9ddcf853a87f1c5c3f44e1
git.kernel.org/...c/a5844227e0f030d2af2d85d4aed10c5eca6ca176