CVE-2026-63906: usb: musb: omap2430: Fix use-after-free in omap2430_probe()
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 27e62532228dc42367bb43ebbcd7bf49d8db2b0d, 6.1, 6.1.176.
Low priority for now. Upgrade to Linux Linux 27e62532228dc42367bb43ebbcd7bf49d8db2b0d, 6.1, 6.1.176 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: usb: musb: omap2430: Fix use-after-free in omap2430_probe() 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.
- Published
- Jul 19, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-416
Report tools
Action score
33
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- fed43efc00ba6ac8c6b95828cd5acfa3d45eca4d, 6.2affected
- 22b60658a90260e3fbd57824e3afe5682c6afcf5 and later · before 632fd888fe33083927e29ef651ac1aba345edd9eaffected · git
- ffbe2feac59b37c8dc536727552b4f375e1b9aec and later · before b987f380620b38c84f054d5ff5c05861a7c2203baffected · git
- ffbe2feac59b37c8dc536727552b4f375e1b9aec and later · before 27e62532228dc42367bb43ebbcd7bf49d8db2b0daffected · git
- ffbe2feac59b37c8dc536727552b4f375e1b9aec and later · before 69f9f2b30af03d9b6e83f78fb0f734b6066d4678affected · git
- ffbe2feac59b37c8dc536727552b4f375e1b9aec and later · before d53e4c41331f57b9fd78cbf3e480c6ce20aea07baffected · git
- ffbe2feac59b37c8dc536727552b4f375e1b9aec and later · before e194ce048f5a6c549b3a23a8c568c6470f40f772affected · git
- 6.1.2 and later · before 6.1.176affected · semver
- 6.0.16 and later · before 6.1affected · semver
- before 6.2not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.0.16 and later · before 6.1
- linux linux kernel6.1.2 and later · before 6.1.176
- linux linux kernel6.2 and later · before 6.6.143
- linux linux kernel6.7 and later · before 6.12.93
- linux linux kernel6.13 and later · before 6.18.35
- linux linux kernel6.19 and later · before 7.0.12
- linux linux kernel7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.12-1 | 7.0.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-63904Jul 19, 2026 · usb: usbtmc: check URB actual_length for interrupt-IN notifications28Monitor
- ← EarlierCVE-2026-63905Jul 19, 2026 · usbip: vudc: Fix use after free bug in vudc_remove due to race condition31Monitor
- Later →CVE-2026-63907Jul 19, 2026 · uio: uio_pci_generic_sva: fix double free of devm_kzalloc() memory31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 27e62532228dc42367bb43ebbcd7bf49d8db2b0d | Vendor (CNA) |
| Linux Linux | 6.1 | Vendor (CNA) |
| Linux Linux | 6.1.176 | Vendor (CNA) |
| Linux Linux | 632fd888fe33083927e29ef651ac1aba345edd9e | Vendor (CNA) |
| Linux Linux | 69f9f2b30af03d9b6e83f78fb0f734b6066d4678 | Vendor (CNA) |
| Linux Linux | b987f380620b38c84f054d5ff5c05861a7c2203b | Vendor (CNA) |
| Linux Linux | d53e4c41331f57b9fd78cbf3e480c6ce20aea07b | Vendor (CNA) |
| Linux Linux | e194ce048f5a6c549b3a23a8c568c6470f40f772 | Vendor (CNA) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/632fd888fe33083927e29ef651ac1aba345edd9e
- git.kernel.org/stable/c/69f9f2b30af03d9b6e83f78fb0f734b6066d4678
- git.kernel.org/stable/c/b987f380620b38c84f054d5ff5c05861a7c2203b
- git.kernel.org/stable/c/d53e4c41331f57b9fd78cbf3e480c6ce20aea07b
- git.kernel.org/stable/c/e194ce048f5a6c549b3a23a8c568c6470f40f772
Vendor advisories and official records. Exploit/PoC links are deliberately left out.