CVE-2026-64349
Last modified
CVE-2026-64349 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: fix dwc3_readl() and dwc3_writel() calls in dwc3_ulpi_setup() The dwc3_ulpi_setup() calls the register read and write calls with dwc3->regs when both these calls take the dwc3 structure directly. Chnage these two calls to fix the following sparse warning, and possibly a nasty bug in the dwc3_ulpi_setup() code: drivers/usb/dwc3/core.c:796:45: warning: incorrect type in argument 1 (different address spaces) drivers/usb/dwc3/core.c:796:45: expected struct dwc3 *dwc drivers/usb/dwc3/core.c:796:45: got void [noderef] __iomem *regs drivers/usb/dwc3/core.c:798:40: warning: incorrect type in argument 1 (different address spaces) drivers/usb/dwc3/core.c:798:40: expected struct dwc3 *dwc drivers/usb/dwc3/core.c:798:40: got void [noderef] __iomem *regs. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: fix dwc3_readl() and dwc3_writel() calls in dwc3_ulpi_setup() The dwc3_ulpi_setup() calls the register read and write calls with dwc3->regs when both these calls take the dwc3 structure directly. Chnage these two calls to fix the following sparse warning, and possibly a nasty bug in the dwc3_ulpi_setup() code: drivers/usb/dwc3/core.c:796:45: warning: incorrect type in argument 1 (different address spaces) drivers/usb/dwc3/core.c:796:45: expected struct dwc3 *dwc drivers/usb/dwc3/core.c:796:45: got void [noderef] __iomem *regs drivers/usb/dwc3/core.c:798:40: warning: incorrect type in argument 1 (different address spaces) drivers/usb/dwc3/core.c:798:40: expected struct dwc3 *dwc drivers/usb/dwc3/core.c:798:40: got void [noderef] __iomem *regs
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 476ee6389120e1900290b46081b3a12b54e05672, < 41a4e80d5af04855e68ac88f5e2cd07fa67287f8; >= 9accc68b1cf0a2b220f51d53641128bb32598070, < 4349e487a1149ff33b65d53427b8aca57f2e4578; >= 9accc68b1cf0a2b220f51d53641128bb32598070, < e0f844d9d74200d311c6438a0f04270834ba5365; >= 6.18.32, < 6.18.40 |
| Linux | Linux | 7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64349?
How severe is CVE-2026-64349?
How do I fix CVE-2026-64349?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64343In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64344In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64345In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64346In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64347In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64348In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64350In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64351In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64352In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64353In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64354In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64355In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2026-64349?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
