CVE-2026-98412
NoneCVSS
—
EPSS
0.2%
Published
Oct 14, 2026
CISA due date
—
Cloudanix analysis
A rare Linux kernel bug could make the computer crash when memory is very low during power-management setup.
- Exploitation
- Local Privilege
- Attacker needs
- Local User
- Complexity
- High
- Impact
- Denial Of Service
- Component
- OS kernel
- Class
- Memory Corruption
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
In the power sequencing subsystem, an allocation failure in pwrseq_unit_setup_deps causes pwrseq_unit_put to invoke pwrseq_unit_release on a struct whose list head was never initialized, so list_del unconditionally dereferences an uninitialized pointer.
Why it matters to the business
A low-probability kernel crash during device power initialization can produce sudden reboots or boot failures on affected systems, increasing operational downtime in environments that rely on the power sequencing framework.
How an attack unfolds
An attacker would need to induce a precise memory-allocation failure inside pwrseq_unit_setup_deps while the unit is only partially constructed; because the trigger requires control over kernel memory pressure and no public exploit exists, the path is considered non-exploitable in practice.
How to fix it
Apply the upstream fix that initializes unit->list immediately after allocation; rebuild and deploy the patched kernel. No downstream fixed-version packages are listed for this change.
How to confirm the fix worked
Confirm the presence of the initialization statement for unit->list right after the allocation site in pwrseq_unit_new; run kernel build tests that exercise pwrseq error paths under memory-pressure simulation.
Typical attack path
- Trigger high memory pressure to force kmalloc failure inside pwrseq_unit_setup_deps
- Allow the error path to call pwrseq_unit_put on the partially-initialized unit
- pwrseq_unit_release performs list_del on the uninitialized list head
- Kernel dereferences invalid memory and panics
How to detect it
Review kernel logs for oops or panic messages referencing pwrseq_unit_release or list_del near power sequencing initialization; no public indicators of active exploitation are known.
What your security team should do
- Prioritize kernel update on systems that use the power-sequencing framework within the next maintenance window
- Monitor upstream stable branches for back-ports of the listed commit
- Include power-sequencing error paths in future kernel fuzzing campaigns
The record
In the Linux kernel, the following vulnerability has been resolved: power: sequencing: fix NULL-pointer dereference in pwrseq_unit_new() If memory allocation fails in pwrseq_unit_setup_deps(), pwrseq_unit_put() is called to release the partially initialized unit. However, we've never initialized unit->list and pwrseq_unit_release() will unconditionally call list_del() on it. Initialize unit->list right after allocating the unit struct.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|