Skip to content
Fencer Intel
no cvss —

CVE-2025-71140 json

media: mediatek: vcodec: Use spinlock for context list protection lock

published 9mo ago modified 4mo ago also EUVD-2026-2476

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 6.6.120, 6.9, 6.12.64, 6.18.4, 6.19
  • linux Debian 13 6.12.69-1
  • linux Debian 14 6.18.5-1

debian advisories DEBIAN-CVE-2025-71140

  • linux Ubuntu 24.04 LTS 6.8.0-110.110
  • linux Ubuntu 25.10 6.17.0-22.22
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1052.55
  • linux-aws Ubuntu 25.10 6.17.0-1012.12
  • linux-gcp Ubuntu 24.04 LTS 6.8.0-1054.57
  • linux-gcp Ubuntu 25.10 6.17.0-1012.12
  • linux-gke Ubuntu 24.04 LTS 6.8.0-1050.56
  • linux-ibm Ubuntu 24.04 LTS 6.8.0-1051.51

ubuntu advisories UBUNTU-CVE-2025-71140

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2025-71140 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-71140 updated

kernel: media: mediatek: vcodec: Use spinlock for context list protection lock

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-09).

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.