Look up another CVE · open CVE-2026-63906 in the interactive tracker
CVE-2026-63906
usb: musb: omap2430: Fix use-after-free in omap2430_probe()
Published 2026-07-19 (3 months ago) by the Linux kernel CNA. Subsystem drivers/usb. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-63906 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.176-1 | Update the kernel and reboot. Fixed in 6.1.176-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.94-1 | Update the kernel and reboot. Fixed in 6.12.94-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
In omap2430_probe(), of_node_put(np) is called prematurely before the last access to np, leading to a use-after-free if the node's reference count drops to zero. Move the of_node_put() calls after the last use of np in both the success and error paths.
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/usb/musb/omap2430.c
- What this is
- OMAP USB SUPPORTMAINTAINERS section matched on drivers/usb/*/*omap* · linux-usb@vger.kernel.org · Orphan
- Kernel module
- omap2430
Check it on the machine
grep -wE 'CONFIG_OF|CONFIG_PCI|CONFIG_USB|CONFIG_USB_GADGET|CONFIG_USB_MUSB_HDRC|CONFIG_USB_MUSB_OMAP2PLUS|CONFIG_USB_PHY|CONFIG_USB_SUPPORT' /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 omap2430Prints 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.
- bookwormMnot 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
- trixieMnot 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, sidMnot 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
- M
- a module where it is built at all; some flavours do not build it
- Build switches
- CONFIG_OF, CONFIG_PCI, CONFIG_USB, CONFIG_USB_GADGET, CONFIG_USB_MUSB_HDRC, CONFIG_USB_MUSB_OMAP2PLUS, CONFIG_USB_PHY, CONFIG_USB_SUPPORT
- 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-07-19 (3 months 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.18%, higher than 6.5% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/usb
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.1.2 | 6.1.176 | 632fd888fe33 |
| 6.2 | 6.6.143 | b987f380620b |
| 6.2 | 6.12.93 | 27e62532228d |
| 6.2 | 6.18.35 | 69f9f2b30af0 |
| 6.2 | 7.0.12 | d53e4c41331f |
| 6.2 | 7.1 | e194ce048f5a |
| 6.0.16 | 0 | 0 |
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 UAF is reached only through local kernel driver probing (boot-time platform device enumeration, module load, or sysfs bind), not via network or USB packet handling. This is the highest defensible attack vector for this platform-driver probe bug.
- AC:LAttack complexity, low
- Once probe runs on affected OMAP hardware, the premature of_node_put() deterministically frees the device_node before subsequent property/IRQ reads on the same pointer, with no race or attacker-uncontrollable timing required.
- PR:NPrivileges required, none
- On OMAP3/OMAP4 systems with the driver built-in, the vulnerable probe path executes automatically at every boot without any software privileges; an attacker only needs the ability to power-cycle or reboot the device (e.g., a public OMAP kiosk or embedded controller).
- UI:NUser interaction, none
- Exploitation requires no victim interaction such as opening files or plugging in USB devices; the bug fires during kernel driver initialization on affected hardware.
- S:UScope, unchanged
- Impact is confined to kernel memory corruption and privilege boundaries within the host kernel; OMAP MUSB is an embedded SoC USB controller, not a hypervisor or cross-VM boundary.
- C:HConfidentiality impact, high
- The use-after-free on a freed device_node structure allows reads of reallocated slab memory through of_property_read_u32() and of_parse_phandle(), enabling kernel information disclosure.
- I:HIntegrity impact, high
- UAF on the device_node heap object can corrupt kernel metadata and be leveraged for controlled writes or code execution through heap grooming during probe.
- A:HAvailability impact, high
- Reading freed device_node memory during probe can cause kernel oops/panic and brick boot on OMAP systems, making the device unavailable until power-cycled or reflashed.