# CVE-2026-64349: linux: In the Linux kernel, the following vulnerability has been resolved:  usb: dwc3: fix dwc3_readl() and dwc3_writel() ca...

CVE-2026-64349 is fixed in linux on 1 platform by DEBIAN-CVE-2026-64349 (version 7.1.4-1), released August 7, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-64349
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0012
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Jul 25, 2026

## 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

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 14 | 7.1.4-1 | [DEBIAN-CVE-2026-64349](https://patchblox.com/security/data/fix/linux/debian-cve-2026-64349.md) | Aug 7, 2026 |

---

Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.