CVE-2025-71140: media: mediatek: vcodec: Use spinlock for context list protection lock
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Fixed version: Linux Linux 2c1ea6214827041f548279c9eda341eda0cc8351, 3e858938b0e659f6ec9ddcf853a87f1c5c3f44e1, 6.6.120.
Low priority for now. Upgrade to Linux Linux 2c1ea6214827041f548279c9eda341eda0cc8351, 3e858938b0e659f6ec9ddcf853a87f1c5c3f44e1, 6.6.120 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 14, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 23aaf824121055ba81b55f75444355bd83c8eb38, 41671f0c0182b2bae74ca7e3b0f155559e3e2fc5, 51c84a8aac6e3b59af2b0e92ba63cabe2e641a2d, 6.9affected
- 0a2dc707aa42214f9c4827bd57e344e29a0841d6 and later · before 2c1ea6214827041f548279c9eda341eda0cc8351affected · git
- 6467cda18c9f9b5f2f9a0aa1e2861c653e41f382 and later · before b92c19675f632a41af1222027a231bc2b7efa7edaffected · git
- 6467cda18c9f9b5f2f9a0aa1e2861c653e41f382 and later · before 3e858938b0e659f6ec9ddcf853a87f1c5c3f44e1affected · git
- 6467cda18c9f9b5f2f9a0aa1e2861c653e41f382 and later · before a5844227e0f030d2af2d85d4aed10c5eca6ca176affected · git
- 6.6.27 and later · before 6.6.120affected · semver
- 6.8.6 and later · before 6.9affected · semver
- before 6.9not affected · semver
- 6.6.120 and later · up to and including 6.6.*not affected · semver
- 6.12.64 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.5-1 | 6.18.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68822Jan 13, 2026 · Input: alps - fix use-after-free bugs caused by dev3_register_work31Monitor
- ← EarlierCVE-2025-71064Jan 13, 2026 · net: hns3: using the num_tqps in the vf driver to apply for resources0Monitor
- Later →CVE-2026-23027Jan 31, 2026 · LoongArch: KVM: Fix kvm_device leak in kvm_pch_pic_destroy()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2c1ea6214827041f548279c9eda341eda0cc8351 | Vendor (CNA) |
| Linux Linux | 3e858938b0e659f6ec9ddcf853a87f1c5c3f44e1 | Vendor (CNA) |
| Linux Linux | 6.6.120 | Vendor (CNA) |
| Linux Linux | 6.9 | Vendor (CNA) |
| Linux Linux | a5844227e0f030d2af2d85d4aed10c5eca6ca176 | Vendor (CNA) |
| Linux Linux | b92c19675f632a41af1222027a231bc2b7efa7ed | Vendor (CNA) |
| debian:linux | 6.12.69-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.