Look up another CVE · open CVE-2026-80649 in the interactive tracker
CVE-2026-80649
firmware: arm_scmi: Fix OOB in scmi_power_name_get()
Published 2026-08-28 (2 months ago) by the Linux kernel CNA. Subsystem drivers/firmware. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-80649 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 | fixed | 6.1.180-1 | Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.100-1 | Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
scmi_power_name_get() does not validate the domain number passed by the external caller, which may lead to an out-of-bounds access. Fix this by returning "unknown" for invalid domains, like scmi_reset_name_get() does.
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/firmware/arm_scmi/power.c
- What this is
- SYSTEM CONTROL & POWER/MANAGEMENT INTERFACE (SCPI/SCMI) Message Protocol driversMAINTAINERS section matched on drivers/firmware/arm_scmi/ · arm-scmi@vger.kernel.org · Maintained
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
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.
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
Signals
- Published
- 2026-08-28 (2 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.18%, higher than 6.6% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/firmware
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 4.17 | 5.15.212 | 01613f5e4ff6 |
| 4.17 | 6.1.178 | ca94597440fa |
| 4.17 | 6.6.145 | 30aa34849453 |
| 4.17 | 6.12.97 | 0db2bb3c948e |
| 4.17 | 6.18.40 | 11daac2817dc |
| 4.17 | 7.1.5 | 11bb771f3c55 |
| 4.17 | 7.2 | f9ef3f66f4b1 |
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
- scmi_power_name_get() is only reachable from kernel-side SCMI power-domain driver probe/registration and other in-kernel callers of scmi_power_proto_ops on ARM/ARM64 SoCs (phones, automotive, embedded); there is no network, Bluetooth, or physical-user input path into this firmware helper.
- AC:LAttack complexity, low
- Once an out-of-range domain index reaches scmi_power_name_get(), the flaw deterministically indexes past pi->dom_info with no races, timing, or uncontrollable memory layout; the attacker fully controls the domain argument supplied to the unchecked pointer arithmetic.
- PR:LPrivileges required, low
- On typical ARM/Android/embedded deployments SCMI power-domain registration runs automatically during boot/driver bind; the vulnerable name_get op is published to external kernel drivers that may pass unchecked domain IDs from device metadata without requiring init-namespace root beyond ordinary local access on those systems.
- UI:NUser interaction, none
- Exploitation requires no victim interaction such as mounting filesystems or opening files; triggering depends only on kernel driver registration paths or module activity, not on actions by an interactive user.
- S:UScope, unchanged
- The out-of-bounds read corrupts/leaks kernel heap metadata within the same kernel security authority; it does not cross VM, container, IOMMU, or firmware trust boundaries in a way that changes CVSS scope.
- C:HConfidentiality impact, high
- scmi_power_name_get() performs an out-of-bounds read of struct power_dom_info entries (including the 64-byte name field) when domain >= num_domains, exposing adjacent kmalloc slab contents and enabling kernel memory disclosure through returned string pointers.
- I:HIntegrity impact, high
- Kernel guidance treats out-of-bounds dom_info indexing as memory corruption; returning a pointer into adjacent heap objects used as genpd names can be leveraged on ARM SCMI deployments for further heap grooming and arbitrary kernel write/control-flow hijack primitives.
- A:HAvailability impact, high
- Indexing far beyond the allocated dom_info array can return pointers into unmapped or non-string memory that fault when dereferenced for sysfs/genpd naming or logging, causing a kernel OOPS/panic and complete loss of availability until reboot.