Answer in brief
CVE-2026-64333 records a Unknown severity vulnerability in USB: serial: digi_acceleport: fix write buffer corruption. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64333 records a Unknown severity vulnerability in USB: serial: digi_acceleport: fix write buffer corruption. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5d9dc88bdf8897788b0eed57113e9eca7fd42ea9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2f296974acc279f05f284441bfe3064074958d11 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e60e4873e9178da9f4f2674e4c2ff085d5a84f79 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <699dfb6917503b3cda4d5da6941cf79c3c1b4c8b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a274b3794fe1852c3d9fe6d900b94053c0b03410 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1243f120790042c2ac92e84e797dacc75fff4366 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a3a13fdc53103b07335918e2cdeb465038a71725 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <24ca1fea8f2753bf33e1d458ec1ae5d9b7796a65 | 5d9dc88bdf8897788b0eed57113e9eca7fd42ea9, 2f296974acc279f05f284441bfe3064074958d11, e60e4873e9178da9f4f2674e4c2ff085d5a84f79, 699dfb6917503b3cda4d5da6941cf79c3c1b4c8b, a274b3794fe1852c3d9fe6d900b94053c0b03410, 1243f120790042c2ac92e84e797dacc75fff4366, a3a13fdc53103b07335918e2cdeb465038a71725, 24ca1fea8f2753bf33e1d458ec1ae5d9b7796a65 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5d9dc88bdf8897788b0eed57113e9eca7fd42ea9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2f296974acc279f05f284441bfe3064074958d11 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e60e4873e9178da9f4f2674e4c2ff085d5a84f79 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <699dfb6917503b3cda4d5da6941cf79c3c1b4c8b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a274b3794fe1852c3d9fe6d900b94053c0b03410 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1243f120790042c2ac92e84e797dacc75fff4366 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a3a13fdc53103b07335918e2cdeb465038a71725 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <24ca1fea8f2753bf33e1d458ec1ae5d9b7796a65 | 5d9dc88bdf8897788b0eed57113e9eca7fd42ea9, 2f296974acc279f05f284441bfe3064074958d11, e60e4873e9178da9f4f2674e4c2ff085d5a84f79, 699dfb6917503b3cda4d5da6941cf79c3c1b4c8b, a274b3794fe1852c3d9fe6d900b94053c0b03410, 1243f120790042c2ac92e84e797dacc75fff4366, a3a13fdc53103b07335918e2cdeb465038a71725, 24ca1fea8f2753bf33e1d458ec1ae5d9b7796a65 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.