CVE-2026-53194

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

USB: serial: kl5kusb105: fix bulk-out buffer overflow

klsi_105_prepare_write_buffer() is called by the generic write path with the bulk-out buffer and its size (bulk_out_size, 64 bytes). It stores a two-byte length header at the start of the buffer and copies the payload from the write fifo starting at buf + KLSI_HDR_LEN, but passes the full buffer size as the number of bytes to copy:

count = kfifo_out_locked(&port->write_fifo, buf + KLSI_HDR_LEN, size, &port->lock);

When the fifo holds at least size bytes, size bytes are copied starting two bytes into the size-byte buffer, writing KLSI_HDR_LEN bytes past its end. Copy at most size - KLSI_HDR_LEN bytes instead, leaving room for the header as safe_serial already does.

Writing bulk_out_size or more bytes to the tty triggers a slab out-of-bounds write, observed with KASAN by emulating the device with dummy_hcd and raw-gadget:

BUG: KASAN: slab-out-of-bounds in kfifo_copy_out+0x83/0xc0 Write of size 64 at addr ffff888112c62202 by task python3 kfifo_copy_out klsi_105_prepare_write_buffer [kl5kusb105] usb_serial_generic_write_start [usbserial] Allocated by task 139: usb_serial_probe [usbserial] The buggy address is located 2 bytes inside of allocated 64-byte region

The out-of-bounds write no longer occurs with this change applied.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

USB: serial: kl5kusb105: fix bulk-out buffer overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bde742b076cbe26ecc89c8c68c76ae076a524d02
generic

USB: serial: kl5kusb105: fix bulk-out buffer overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a1288cd700f721c1a119c4f1e8efa234e59caada
generic

USB: serial: kl5kusb105: fix bulk-out buffer overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96d47e40bf9db4a9efd5c8fb53287a508d165f14
generic

USB: serial: kl5kusb105: fix bulk-out buffer overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70d86e355c564b5510fde61361df014f5476c83e
generic

USB: serial: kl5kusb105: fix bulk-out buffer overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/60af1fd82983c26604102e63a3fcc822c186cceb
generic

USB: serial: kl5kusb105: fix bulk-out buffer overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/372f33ebed747d91870f57c0a2e62884a870bffa
generic

USB: serial: kl5kusb105: fix bulk-out buffer overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/14147b7963685957839c76ba8094924e22777d79
generic

USB: serial: kl5kusb105: fix bulk-out buffer overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0a57320f71941d4e0b1307453c9a1f0939afe666

Vendor Advisories for CVE-2026-53194(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 83× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 304 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 19:40 UTCEG score recompute
  11. 2026-08-30 19:40 UTCVendor advisory
  12. 2026-08-30 19:40 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-28 02:53 UTCEG score recompute
  17. 2026-08-28 02:53 UTCVendor advisory
  18. 2026-08-28 02:53 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 00:27 UTCEG score recompute
  23. 2026-08-25 00:27 UTCVendor advisory
  24. 2026-08-25 00:27 UTCGHSA enrichment
  25. 2026-08-24 13:15 UTCEG score recompute
Show 75 more
  1. 2026-08-24 13:15 UTCVendor advisory
  2. 2026-08-24 13:15 UTCGHSA enrichment
  3. 2026-08-23 20:53 UTCVendor advisory
  4. 2026-08-23 20:53 UTCGHSA enrichment
  5. 2026-08-23 09:41 UTCEG score recompute
  6. 2026-08-23 09:41 UTCVendor advisory
  7. 2026-08-23 09:41 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 22:30 UTCVendor advisory
  10. 2026-08-22 22:30 UTCGHSA enrichment
  11. 2026-08-22 10:46 UTCEG score recompute
  12. 2026-08-22 10:46 UTCVendor advisory
  13. 2026-08-22 10:46 UTCGHSA enrichment
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 17:26 UTCGHSA enrichment
  16. 2026-08-21 05:35 UTCEG score recompute
  17. 2026-08-21 05:35 UTCVendor advisory
  18. 2026-08-21 05:35 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 18:22 UTCVendor advisory
  21. 2026-08-20 18:22 UTCGHSA enrichment
  22. 2026-08-20 07:10 UTCEG score recompute
  23. 2026-08-20 07:10 UTCVendor advisory
  24. 2026-08-20 07:10 UTCGHSA enrichment
  25. 2026-08-19 17:04 UTCEPSS rescore
  26. 2026-08-19 12:44 UTCVendor advisory
  27. 2026-08-19 12:44 UTCGHSA enrichment
  28. 2026-08-19 01:33 UTCEG score recompute
  29. 2026-08-19 01:33 UTCVendor advisory
  30. 2026-08-19 01:33 UTCGHSA enrichment
  31. 2026-08-18 13:48 UTCEPSS rescore
  32. 2026-08-17 13:47 UTCEPSS rescore
  33. 2026-08-17 07:15 UTCVendor advisory
  34. 2026-08-17 07:15 UTCGHSA enrichment
  35. 2026-08-16 20:04 UTCEG score recompute
  36. 2026-08-16 20:04 UTCVendor advisory
  37. 2026-08-16 20:04 UTCGHSA enrichment
  38. 2026-08-16 14:56 UTCEPSS rescore
  39. 2026-08-16 07:49 UTCEG score recompute
  40. 2026-08-16 07:49 UTCVendor advisory
  41. 2026-08-16 07:49 UTCGHSA enrichment
  42. 2026-08-16 02:14 UTCEPSS rescore
  43. 2026-08-15 20:38 UTCVendor advisory
  44. 2026-08-15 20:38 UTCGHSA enrichment
  45. 2026-08-15 09:26 UTCEG score recompute
  46. 2026-08-15 09:26 UTCVendor advisory
  47. 2026-08-15 09:26 UTCGHSA enrichment
  48. 2026-08-15 01:30 UTCEPSS rescore
  49. 2026-08-14 22:14 UTCVendor advisory
  50. 2026-08-14 22:14 UTCGHSA enrichment
  51. 2026-08-14 11:02 UTCGHSA enrichment
  52. 2026-08-13 23:51 UTCEG score recompute
  53. 2026-08-13 23:51 UTCVendor advisory
  54. 2026-08-13 23:51 UTCGHSA enrichment
  55. 2026-08-13 22:00 UTCEPSS rescore
  56. 2026-08-13 12:39 UTCVendor advisory
  57. 2026-08-13 12:39 UTCGHSA enrichment
  58. 2026-08-13 01:17 UTCGHSA enrichment
  59. 2026-08-12 14:05 UTCEG score recompute
  60. 2026-08-12 14:05 UTCVendor advisory
  61. 2026-08-12 14:05 UTCGHSA enrichment
  62. 2026-08-12 13:51 UTCEPSS rescore
  63. 2026-08-12 02:50 UTCVendor advisory
  64. 2026-08-12 02:50 UTCGHSA enrichment
  65. 2026-08-11 15:39 UTCEG score recompute
  66. 2026-08-11 15:39 UTCVendor advisory
  67. 2026-08-11 15:39 UTCGHSA enrichment
  68. 2026-08-11 04:27 UTCEG score recompute
  69. 2026-08-11 04:27 UTCVendor advisory
  70. 2026-08-11 04:27 UTCGHSA enrichment
  71. 2026-08-11 00:00 UTCEPSS rescore
  72. 2026-08-10 17:16 UTCGHSA enrichment
  73. 2026-08-10 05:29 UTCVendor advisory
  74. 2026-08-10 05:29 UTCGHSA enrichment
  75. 2026-08-09 18:17 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-53194?
CVE-2026-53194 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: USB: serial: kl5kusb105: fix bulk-out buffer overflow klsi105preparewritebuffer() is called by the generic write path with the bulk-out buffer and its size (bulkoutsize, 64 bytes). It stores a two-byte length header at the start of…
When was CVE-2026-53194 disclosed?
CVE-2026-53194 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53194 actively exploited?
CVE-2026-53194 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53194?
CVE-2026-53194 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53194?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53194, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53194

Explore →

Is Your Infrastructure Affected by CVE-2026-53194?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.