CVE-2026-98411: power: sequencing: fix NULL-pointer dereference in pwrseq_device_register()
In the Linux kernel, the following vulnerability has been resolved:
power: sequencing: fix NULL-pointer dereference in pwrseqdeviceregister()
If devsetname() fails in pwrseqdeviceregister(), we jump to the errputpwrseq label before initializing pwrseq->targets. pwrseqrelease() will try to iterate over targets unconditionally and subsequently dereference an invalid pointer. Move the call to devsetname() after the list head is initialized.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
Under what condition can this NULL-pointer dereference occur?
It can occur when dev_set_name() fails during pwrseq_device_register(). The failure path releases the power-sequencing object before its targets list head has been initialized.
Is normal successful device registration affected?
The described dereference is limited to the error path triggered by a dev_set_name() failure. The data does not indicate that successful registrations reach the vulnerable release path.
What change resolves the issue?
The fix initializes the targets list head before calling dev_set_name(). This ensures pwrseq_release() can safely iterate the list if naming fails.