CVE-2026-43207: media: mtk-mdp: Fix error handling in probe function
In the Linux kernel, the following vulnerability has been resolved:
media: mtk-mdp: Fix error handling in probe function
Add mtk_mdp_unregister_m2m_device() on the error handling path to prevent
resource leak.
Add check for the return value of vpu_get_plat_device() to prevent null
pointer dereference. And vpu_get_plat_device() increases the reference
count of the returned platform device. Add platform_device_put() to
prevent reference leak.
Security readout for executives and security teams
Plain-English summary
A Linux MediaTek media-processing driver can mishandle failures while starting, causing a null-pointer dereference or leaked resources. The supplied CVSS rating is 7.8 (high) and assumes a local, low-privileged attacker could affect confidentiality, integrity, and availability. The source bundle does not explain how those impacts were demonstrated.
Executive priority
Treat as a high-priority targeted kernel update, especially for MediaTek-based systems permitting untrusted local users or workloads. It is less urgent for systems without the driver or relevant hardware. Validate applicability promptly; the bundle provides no evidence of active exploitation.
Technical view
The mtk-mdp probe error paths failed to unregister an M2M device, validate vpu_get_plat_device() before dereferencing its result, and release the platform-device reference. Linux stable commits add cleanup, a return-value check, and platform_device_put(). Exact vulnerable version boundaries are unclear in the supplied affected-version data.
Likely exposure
Exposure is most likely limited to Linux systems containing and using the MediaTek MDP media driver. Risk depends on kernel version, configuration, hardware, and whether the driver probes. The supplied version list is ambiguous, so do not determine exposure from version numbers alone.
Exploitation context
The CVSS vector describes local access, low privileges, low complexity, and no user interaction. CVE is not marked as CISA KEV in the bundle, and no cited source reports active exploitation or a public exploit. Absence from KEV does not prove exploitation is impossible.
Researcher notes
The fix addresses probe-time cleanup, NULL checking, and reference management. The CVSS claims complete confidentiality, integrity, and availability impact, but the description only directly identifies null dereference and resource leaks. No CWE, exploitability analysis, affected configuration, or proof of privilege escalation is supplied. Branch-specific commit ancestry is the strongest validation method.
Mitigation direction
Install a vendor-supported kernel containing the applicable Linux stable fix commit.
Check distribution or device-vendor guidance for the exact corrected package and branch.
Prioritize systems where the MediaTek MDP driver is present and active.
If updates are unavailable, request vendor-supported mitigations; none are documented in the supplied sources.
Validation and detection
Record the running kernel version, build, architecture, and vendor package revision.
Determine whether the MediaTek MDP driver is built, loadable, or active on the system.
Confirm the vendor kernel includes the applicable referenced stable commit.
Review vendor advisories because the supplied affected-version boundaries are ambiguous.
After updating, verify the expected kernel is running and the driver initializes normally.
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-2026-43207 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.