CVE-2026-80751
nicheUse of uninitialized pointer in Linux kernel MediaTek MFG power domain driver
CVE-2026-80751 is a use-of-uninitialized-variable flaw in the MediaTek MFG (GPU) power domain driver (pmdomain: mediatek: mfg) of the Linux kernel. In mtk_mfg_attach_dev(), the variable prev_o is read on the first loop iteration before it is ever assigned, so the code may dereference a stale or invalid pointer, potentially faulting the kernel or incorrectly skipping the first OPP (operating performance point). The flaw is triggered locally whenever a device is attached to the affected power domain and the driver enumerates OPPs; no user interaction or network access is required (CVSS 3.1: AV:L/PR:L). An attacker would at most gain a local denial of service (kernel fault) or incorrect power/OPP handling; there is no evidence of privilege escalation. Affected users are Linux systems running on MediaTek SoCs whose kernels include this MFG power-domain driver; no known exploitation, public PoC, or KEV listing exists (EPSS 0.2%).
What to do: Update affected Linux kernels to a version that includes the fix (prev_o initialized to NULL in mtk_mfg_attach_dev()) or the corresponding stable-branch backport from your distribution once available; check whether your kernel build enables the MediaTek MFG/mediatek pmdomain option and whether you run on an affected MediaTek SoC. Given the local attack vector, lack of known exploitation, and low EPSS (0.2%), patching in your normal maintenance window is reasonable.
| Linux kernel pmdomain: mediatek: mfg (MediaTek GPU power domain driver, mtk_mfg_attach_dev) | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
In the Linux kernel, the following vulnerability has been resolved: pmdomain: mediatek: mfg: initialize prev_o in mtk_mfg_attach_dev() mtk_mfg_attach_dev() reads prev_o on the first iteration of its loop, in "if (prev_o && prev_o->freq == o->freq)", before prev_o is assigned at the end of the loop body. On that first iteration, evaluating prev_o reads an indeterminate value. If it is non-NULL, the condition dereferences a stale or invalid pointer, potentially faulting or incorrectly skipping the first OPP. Initialize prev_o to NULL. This matches the intent as well: there is no previous OPP to compare against on the first iteration. Found with Clang's -Wconditional-uninitialized.
- Vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
In the news0 stories
No ingested article mentions this CVE yet.