CVE-2026-64333: Linux kernel · USB: serial: digi_acceleport: fix write buffer corruption
Source GCVE Database
Not known to be exploited · CVSS 7.8 High · fixed in e60e4873e9178da9f4f2674e4c2ff085d5a84f79 : patch Linux kernel soon.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e60e4873e9178da9f4f2674e4c2ff085d5a84f79, a274b3794fe1852c3d9fe6d900b94053c0b03410, a3a13fdc53103b07335918e2cdeb465038a71725 +5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
Users should monitor official Linux kernel updates for the fix addressing this issue. Until patched, avoid using affected USB serial devices if possible.
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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-64333 (opens in a new tab)
- git.kernel.org/stable/c/1243f120790042c2ac92e84e797dacc75fff4366 (opens in a new tab)
- git.kernel.org/stable/c/24ca1fea8f2753bf33e1d458ec1ae5d9b7796a65 (opens in a new tab)
- git.kernel.org/stable/c/2f296974acc279f05f284441bfe3064074958d11 (opens in a new tab)
- git.kernel.org/stable/c/5d9dc88bdf8897788b0eed57113e9eca7fd42ea9 (opens in a new tab)
- git.kernel.org/stable/c/699dfb6917503b3cda4d5da6941cf79c3c1b4c8b (opens in a new tab)
- git.kernel.org/stable/c/a274b3794fe1852c3d9fe6d900b94053c0b03410 (opens in a new tab)
- git.kernel.org/stable/c/a3a13fdc53103b07335918e2cdeb465038a71725 (opens in a new tab)
- git.kernel.org/stable/c/e60e4873e9178da9f4f2674e4c2ff085d5a84f79 (opens in a new tab)