Skip to main content
VulnerabilityPublished Updated

CVE-2026-64333: Linux kernel · USB: serial: digi_acceleport: fix write buffer corruption

Affects Linux kernelSource CVE Database V5

0

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

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
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.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < e60e4873e9178da9f4f2674e4c2ff085d5a84f79
Fixed in
  • e60e4873e9178da9f4f2674e4c2ff085d5a84f79
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < a274b3794fe1852c3d9fe6d900b94053c0b03410
Fixed in
  • a274b3794fe1852c3d9fe6d900b94053c0b03410
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < a3a13fdc53103b07335918e2cdeb465038a71725
Fixed in
  • a3a13fdc53103b07335918e2cdeb465038a71725
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 1243f120790042c2ac92e84e797dacc75fff4366
Fixed in
  • 1243f120790042c2ac92e84e797dacc75fff4366
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 699dfb6917503b3cda4d5da6941cf79c3c1b4c8b
Fixed in
  • 699dfb6917503b3cda4d5da6941cf79c3c1b4c8b
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 24ca1fea8f2753bf33e1d458ec1ae5d9b7796a65
Fixed in
  • 24ca1fea8f2753bf33e1d458ec1ae5d9b7796a65

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

Community reviews

Loading reviews…