Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-71140media: mediatek: vcodec: Use spinlock for context list protection lock

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.19% · top 92% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 0a2dc707aa42214f9c4827bd57e344e29a0841d6 – < 2c1ea6214827041f548279c9eda341eda0cc8351
    • affected 6467cda18c9f9b5f2f9a0aa1e2861c653e41f382 – < b92c19675f632a41af1222027a231bc2b7efa7ed
    • affected 6467cda18c9f9b5f2f9a0aa1e2861c653e41f382 – < 3e858938b0e659f6ec9ddcf853a87f1c5c3f44e1
    • affected 6467cda18c9f9b5f2f9a0aa1e2861c653e41f382 – < a5844227e0f030d2af2d85d4aed10c5eca6ca176
    • affected 23aaf824121055ba81b55f75444355bd83c8eb38
    • affected 41671f0c0182b2bae74ca7e3b0f155559e3e2fc5
    • affected 51c84a8aac6e3b59af2b0e92ba63cabe2e641a2d
    • affected 6.6.27 – < 6.6.120
    • affected 6.8.6 – < 6.9
  • Linux · Linux

    • affected 6.9
    • unaffected < 6.9
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.64 – ≤ 6.12.*
    • unaffected 6.18.4 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-71140 badge
[![CVE-2025-71140](https://cveledger.app/badge/CVE-2025-71140.svg)](https://cveledger.app/cve/CVE-2025-71140)

Record last updated .