Look up another CVE · open CVE-2026-89504 in the interactive tracker
CVE-2026-89504
regulator: as3722_get_regulator_dt_data: fix premature of_node_put leaving dangling of_node pointer
Published 2026-09-11 (37 days ago) by the Linux kernel CNA. Subsystem drivers/regulator. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-89504 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 | fixedDLA-4841-1 · 2026-10-17 · text | 6.1.190-1 | Update the kernel and reboot. DLA-4841-1 shipped the fix on 2026-10-17, in 6.1.190-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
In as3722_get_regulator_dt_data(), of_get_child_by_name() acquires a reference on np, which is then assigned to pdev->dev.of_node. The function immediately calls of_node_put(np), releasing the reference and leaving pdev->dev.of_node as a dangling pointer. Remove the of_node_put(np) call to let the device hold the reference.
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/regulator/as3722-regulator.c
- What this is
- VOLTAGE AND CURRENT REGULATOR FRAMEWORKMAINTAINERS section matched on drivers/regulator/ · linux-kernel@vger.kernel.org · Supported
Check it on the machine
grep -wE 'CONFIG_REGULATOR|CONFIG_REGULATOR_AS3722' /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.
- bookwormYnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/arm64, arm64/cloud-arm64, arm64/rt/arm64, i386/686, i386/686-pae, i386/rt/686-pae, ppc64el/powerpc64le
- trixieYnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armel/rpi, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- forky, sidYnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- bookworm · linux-6.12Ynot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k
- Y
- built in where it is built at all; some flavours do not build it
- Build switches
- CONFIG_REGULATOR, CONFIG_REGULATOR_AS3722
- 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-11 (37 days 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.14%, higher than 3.1% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/regulator
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 3.13 | 5.10.270 | d9b1407477fb |
| 3.13 | 5.15.221 | bd5606e9da1a |
| 3.13 | 6.1.188 | 0bde4f140e90 |
| 3.13 | 6.6.157 | eda08b6bd64f |
| 3.13 | 6.12.109 | d3c1316d84e0 |
| 3.13 | 6.18.50 | 95342d26f9c6 |
| 3.13 | 7.2.4 | 8648e29e5c01 |
| 3.13 | 7.3 | f9324d670ae0 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4841-1 | 2026-10-17 | bookworm 6.1.190-1 | tracker |
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
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
- The dangling of_node is created only on the local as3722-regulator platform probe path (I2C MFD as3722_i2c_probe → mfd_add_devices → as3722_regulator_probe → as3722_get_regulator_dt_data); the onboard AMS AS3722 PMIC is not reached via network packets, Bluetooth, or USB enumeration.
- AC:LAttack complexity, low
- On affected Tegra boards the required regulators DT child exists, so of_get_child_by_name() then the premature of_node_put() runs deterministically at every probe with no race; with OF_OVERLAY (arm64 defconfig) the node can be freed while the device still holds the pointer.
- PR:NPrivileges required, none
- tegra_defconfig builds MFD_AS3722 and REGULATOR_AS3722 in, so the vulnerable probe runs automatically at boot on Chromebooks (nyan), Jetson TK1, Toradex Apalis, and similar embedded systems with no capability check; an attacker only needs to power-cycle a shared kiosk or device.
- UI:NUser interaction, none
- Driver initialization and the of_node_put() run unattended during kernel boot on affected hardware; no victim action such as mounting a filesystem, opening a device, or plugging in USB is required.
- S:UScope, unchanged
- The use-after-free corrupts kernel device_node/kobject memory on the host; AS3722 is a board PMIC regulator driver and does not cross a VM, IOMMU, or other security-authority boundary.
- C:HConfidentiality impact, high
- The premature of_node_put() leaves pdev->dev.of_node dangling; a later put on device release or DT overlay teardown can free the device_node while the driver and OF core still use it, enabling reads of reallocated slab memory.
- I:HIntegrity impact, high
- Use-after-free of the device_node heap object (kobject, fwnode, property and parent/child links) can be turned into an arbitrary write and control-flow hijack via heap reuse, matching scoring guidance that UAF is Integrity High.
- A:HAvailability impact, high
- Dereferencing the dangling of_node during regulator registration, sysfs, overlay removal, or platform_device_release() can oops or panic the kernel, including at boot on systems where AS3722 supplies CPU and core rails.