Look up another CVE · open CVE-2026-93265 in the interactive tracker
CVE-2026-93265
PCI/pwrctrl: tc9563: Fix parsing the integrated Ethernet MAC Endpoint node
Published 2026-09-24 (24 days ago) by the Linux kernel CNA. Subsystem drivers/pci. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-93265 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.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. |
The vulnerability
What the bug is
DSP3 has an integrated Ethernet MAC Endpoint which has its own set of config registers for configuring settings such as ASPM. The Endpoint device has two physical functions and those two functions share the same settings. Parse the Endpoint node under DSP3 instead of parsing both functions. The existing parsing logic also has one OOB issue as parsing both functions will result in accessing past the tc9563_pwrctrl->cfg array.
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/pci/pwrctrl/pci-pwrctrl-tc9563.c
- What this is
- PCI POWER CONTROLMAINTAINERS section matched on drivers/pci/pwrctrl/* · linux-pci@vger.kernel.org · Maintained
- Kernel module
- pci_pwrctrl_tc9563
Check it on the machine
grep -wE 'CONFIG_PCI|CONFIG_PCI_PWRCTRL_TC9563' /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.
lsmod | grep -w pci_pwrctrl_tc9563Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
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 2 releases, so nothing is claimed about those.
- bookworm, trixie?
- forky, sidMnot 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
- M
- a module 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_PCI, CONFIG_PCI_PWRCTRL_TC9563
- 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-24 (24 days ago)source
- CVSS
- 7.7 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.14%, higher than 3.2% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/pci
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.19 | 7.2.6 | 972c771674e8 |
| 6.19 | 7.3 | 6e5e6c2194b2 |
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
- tc9563_pwrctrl_parse_device_dt() is reached from tc9563_pwrctrl_probe() after qcom_pcie_host_init() (also pci-imx6/mediatek-gen3) calls pci_pwrctrl_create_devices() and of_platform_device_create() binds compatible pci1179,0623. The overflowed cfg[] slot is filled from that local OF node (DSP3 ethernet children), not from a network or USB payload.
- AC:LAttack complexity, low
- In-tree qcs6490-rb3gen2.dts and qcs6490-thundercomm-minipc-g1iot.dts put two children (pci@0,0 and pci@0,1) under pcie@3,0. The pre-fix DSP3 loop does port++ then tc9563_pwrctrl_parse_device_dt() for each child, so the second child always uses port==5 past cfg[TC9563_MAX]. No race.
- PR:NPrivileges required, none
- tc9563_pwrctrl_probe() has no capable() check. PCI_PWRCTRL_TC9563 defaults m on ARCH_QCOM, and qcom_pcie_host_init() → pci_pwrctrl_create_devices() binds the pci1179,0623 node during PCIe host probe on those boards, so the cfg[] overflow runs without sysfs bind or credentials.
- UI:NUser interaction, none
- qcom_pcie_host_init() creates the pwrctrl platform device and tc9563_pwrctrl_probe() walks for_each_child_of_node_scoped() during driver-core probe; no other user must mount a filesystem, open a device, or plug the switch.
- S:UScope, unchanged
- The overflowed cfg[port] store and the overlapping reset_gpio/adapter/client fields are in the host-kernel struct tc9563_pwrctrl allocated in tc9563_pwrctrl_probe(); this is not a KVM/Xen guest-to-host escape or an IOMMU/DMA bypass.
- C:NConfidentiality impact, none
- On the in-tree DSP3 ethernet nodes, of_property_read_u32() of aspm-l0s-entry-delay-ns/aspm-l1-entry-delay-ns returns -EINVAL and does not store. The OOB store is cfg->disable_dfe=false (one zero byte into adapter). Later i2c_put_adapter() faults on that non-canonical pointer without copying kernel memory to userspace.
- I:HIntegrity impact, high
- tc9563_pwrctrl_parse_device_dt() writes through &tc9563->cfg[port] when the second DSP3 child increments port to 5, past cfg[TC9563_MAX-1]. That out-of-bounds store overwrites the following adapter (and reset_gpio if delay properties are present) pointers in struct tc9563_pwrctrl, a kernel OOB write.
- A:HAvailability impact, high
- After the port==5 overwrite, tc9563_pwrctrl_remove() and the probe error path call i2c_put_adapter(tc9563->adapter) (or put_device(&adapter->dev)), which dereferences the corrupted adapter pointer and oopses or panics the host.