LiveActive security incident?Get immediate response
CVE Record

CVE-2025-23160: media: mediatek: vcodec: Fix a resource leak related to the scp device in FW initialization

In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Fix a resource leak related to the scp device in FW initialization On Mediatek devices with a system companion processor (SCP) the mtk_scp structure has to be removed explicitly to avoid a resource leak. Free the structure in case the allocation of the firmware structure fails during the firmware initialization.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A Linux MediaTek video-codec initialization error can leave an SCP-related kernel structure allocated when firmware setup fails. This wastes resources and may contribute to instability, but the supplied sources do not quantify impact, attack feasibility, or severity.

Executive priority

Treat this as targeted kernel maintenance rather than an emergency based on current evidence. Promptly investigate affected MediaTek fleets with instability or repeated initialization failures, while scheduling vendor-confirmed updates through normal patching processes.

Technical view

The MediaTek vcodec firmware initialization error path does not explicitly release the mtk_scp structure after firmware-structure allocation fails. Referenced Linux stable commits add the missing cleanup. The flaw is relevant only where the affected MediaTek vcodec and system companion processor functionality is present.

Likely exposure

Exposure is likely limited to Linux-based MediaTek devices using the vcodec driver with an SCP. Confirm exposure by mapping each vendor or distribution kernel build to the referenced stable fixes; the supplied version data alone does not provide a clear fleet-level determination.

Exploitation context

The record is not marked as KEV, and the supplied sources provide no evidence of active exploitation, public weaponization, or a remote attack path. Triggering requires firmware-structure allocation failure during initialization; whether an attacker can induce that condition is not established.

Researcher notes

The documented defect is a cleanup omission on a firmware-initialization allocation-failure path. Important unanswered questions include error-path reachability, repeatability, resource-exhaustion consequences, and attacker influence over allocation failure. No CVSS score, CWE classification, or demonstrated security impact is supplied.

Mitigation direction

  • Inventory Linux MediaTek devices using the vcodec driver and system companion processor.
  • Ask device or distribution vendors whether their kernel contains the applicable referenced stable fix.
  • Install the vendor-supported kernel or firmware update incorporating the fix.
  • Prioritize systems showing repeated video-codec firmware initialization failures or resource pressure.

Validation and detection

  • Record each device's running kernel build, distribution package revision, and vendor patch level.
  • Confirm whether MediaTek vcodec and SCP functionality is present and enabled.
  • Map the deployed kernel branch to its applicable referenced stable commit.
  • Review system logs for recurring video-codec firmware initialization failures.
  • After updating, verify the applicable fix is present and initialization failures do not recur.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-23160 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
11Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxac79a923365ae1e524398087cf16313cdbd7a144, 19ef02106c990bf4235365a08b9d8d2fee37272a, eeb62bb4ca22db17f7dfe8fb8472e0442df3d92f, f066882293b5ad359e44c4ed24ab1811ffb0b354, 53dbe08504442dc7ba4865c09b3bbf5fe849681b, 53dbe08504442dc7ba4865c09b3bbf5fe849681b, 53dbe08504442dc7ba4865c09b3bbf5fe849681b, 53dbe08504442dc7ba4865c09b3bbf5fe849681b, 3a693c7e243b932faee5c1fb728efa73f0abc39b, 6.1.130, 6.6.36, 6.9.7unaffected
LinuxLinux6.10, 0, 6.1.153, 6.6.88, 6.12.24, 6.13.12, 6.14.3, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.