Look up another CVE · open CVE-2026-80750 in the interactive tracker
CVE-2026-80750
pmdomain: mediatek: fix remaining %pOF after of_node_put()
Published 2026-09-03 (2 months ago) by the Linux kernel CNA. Subsystem drivers/pmdomain. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-80750 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
scpsys_get_bus_protection_legacy() looks up several legacy bus protection regmaps from device-tree nodes. Two error paths put the device node before checking whether the regmap lookup failed, but still pass that node to dev_err_probe() with %pOF on failure. If of_node_put() drops the last reference, the later %pOF formatting can dereference a freed device node. Keep the node reference until after the error message has been emitted in the infracfg and SMI lookup paths. Also drop the SMI node before returning when the SMI phandle is missing.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/pmdomain/mediatek/mtk-pm-domains.c
- What this is
- GENERIC PM DOMAINSMAINTAINERS section matched on drivers/pmdomain/ · linux-pm@vger.kernel.org · Supported
Check it on the machine
grep -wE 'CONFIG_MTK_SCPSYS_PM_DOMAINS|CONFIG_PM_GENERIC_DOMAINS' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixieYnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/cloud-arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- forky, sidYnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- ?
- not established - no Makefile entry for the affected file
- Y
- built in where it is built at all; some flavours do not build it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_MTK_SCPSYS_PM_DOMAINS, CONFIG_PM_GENERIC_DOMAINS
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-03 (2 months ago)source
- CVSS
- 8.4 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.19%, higher than 8.4% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/pmdomain
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.18 | 6.18.46 | 970b9c83a07c |
| 6.18 | 7.1.10 | 10bf2d7261d7 |
| 6.18 | 7.2 | 3e013bc8b941 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- scpsys_probe() runs only via the local platform driver model (boot-time builtin probe, deferred-probe retries); no network, adjacent-network, or physical bus path reaches scpsys_get_bus_protection_legacy(), and exploiting the freed device_node requires local heap interaction in kernel context.
- AC:LAttack complexity, low
- On affected MediaTek SoCs using legacy DT without access-controllers, EPROBE_DEFER from syscon not yet registered deterministically hits the premature of_node_put() error paths during boot probe retries; an attacker with DT overlay can also craft failing regmap lookups at will with no race.
- PR:NPrivileges required, none
- The vulnerable sequence executes automatically during kernel init when the builtin mtk-power-controller platform driver probes on MediaTek phones, Chromebooks, and embedded boards; no credentials, capabilities, or user-namespace privileges are checked on this driver probe path.
- UI:NUser interaction, none
- Probe and deferred-probe retries run unattended at boot on affected hardware; no administrator action, mount, file open, or other user interaction is required to reach the error path that dereferences the released device_node.
- S:UScope, unchanged
- The corrupted device_node, its kobject, and OF tree traversal all execute entirely within kernel context on the same security authority; no VM escape, IOMMU boundary bypass, or sandbox crossing occurs.
- C:HConfidentiality impact, high
- Use-after-free of device_node in dev_err_probe()'s %pOF formatting reads freed heap memory (full_name, compatible strings, phandle, flags) via device_node_string(), enabling kernel pointer leaks and arbitrary memory disclosure per UAF scoring guidance.
- I:HIntegrity impact, high
- UAF of device_node permits reclaiming the embedded fwnode_handle/kobject; corrupted ops tables, ktype->release callbacks, and parent/child/sibling links provide exploitable arbitrary write and control-flow hijack primitives consistent with comparable of_node UAF issues.
- A:HAvailability impact, high
- Dereferencing a freed device_node during %pOF formatting can oops or panic the kernel during power-domain probe on affected MediaTek hardware; UAF bugs inherently threaten availability even when not fully weaponized, and failed probe can block power management bring-up.