Kernel memory corruption via premature device-node release
Published Jul 19, 2026 · Updated Jul 19, 2026
Use-after-free in the OMAP2430 MUSB driver in Linux Kernel 6.2 allows local users to corrupt kernel memory during platform-device probing. The omap2430_probe() function releases the np device-node reference before later property and IRQ reads, leaving a freed node reachable through the stale pointer. The path executes locally during boot-time OMAP enumeration, module loading, or sysfs binding; memory corruption can crash the kernel or compromise data.
Summary
What happened
Use-after-free in the OMAP2430 MUSB driver in Linux Kernel 6.2 allows local users to corrupt kernel memory during platform-device probing. The omap2430_probe() function releases the np device-node reference before later property and IRQ reads, leaving a freed node reachable through the stale pointer. The path executes locally during boot-time OMAP enumeration, module loading, or sysfs binding; memory corruption can crash the kernel or compromise data.
The record
- CVE
- CVE-2026-63906
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=22b60658a90260e3fbd57824e3afe5682c6afcf5 <632fd888fe33083927e29ef651ac1aba345edd9e
- Affected versionversion=6.0.16 <6.1
- Affected versionversion=6.1.2 <6.1.176
- Affected versionversion=6.2
- Affected versionversion=fed43efc00ba6ac8c6b95828cd5acfa3d45eca4d
- Affected versionversion=ffbe2feac59b37c8dc536727552b4f375e1b9aec <27e62532228dc42367bb43ebbcd7bf49d8db2b0d
- Affected versionversion=ffbe2feac59b37c8dc536727552b4f375e1b9aec <69f9f2b30af03d9b6e83f78fb0f734b6066d4678
- Affected versionversion=ffbe2feac59b37c8dc536727552b4f375e1b9aec <b987f380620b38c84f054d5ff5c05861a7c2203b
- Affected versionversion=ffbe2feac59b37c8dc536727552b4f375e1b9aec <d53e4c41331f57b9fd78cbf3e480c6ce20aea07b
- Affected versionversion=ffbe2feac59b37c8dc536727552b4f375e1b9aec <e194ce048f5a6c549b3a23a8c568c6470f40f772
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo