Skip to main content
VulnerabilityPublished Updated

CVE-2026-53196: Linux kernel · USB: serial: io_ti: fix heap overflow in get_manuf_info()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium · fixed in f96cf7bf9fbf15d7fcf0c91fec47ba8a010369ea : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
ADP (redhat-SADP)CVSS 3.16.8
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
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in f96cf7bf9fbf15d7fcf0c91fec47ba8a010369ea, e168db91442b94e64fa82a7dd297983d48ea5cc0, d214d2341d4f9f447e36a7d012cdf6a6631a55f1 +5
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < f96cf7bf9fbf15d7fcf0c91fec47ba8a010369ea
Fixed in
  • f96cf7bf9fbf15d7fcf0c91fec47ba8a010369ea
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < e168db91442b94e64fa82a7dd297983d48ea5cc0
Fixed in
  • e168db91442b94e64fa82a7dd297983d48ea5cc0
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < d214d2341d4f9f447e36a7d012cdf6a6631a55f1
Fixed in
  • d214d2341d4f9f447e36a7d012cdf6a6631a55f1
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < d92f17af7097d10bdeddf26f66f34b354104b277
Fixed in
  • d92f17af7097d10bdeddf26f66f34b354104b277
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < cfd634f6dfd40c49a84f9bddc2867a80e2e2623a
Fixed in
  • cfd634f6dfd40c49a84f9bddc2867a80e2e2623a
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < b849f30d1a9e66aae6b715aaef66e427390cb081
Fixed in
  • b849f30d1a9e66aae6b715aaef66e427390cb081

Description

In the Linux kernel, the following vulnerability has been resolved: USB: serial: io_ti: fix heap overflow in get_manuf_info() get_manuf_info() reads le16_to_cpu(rom_desc->Size) bytes from the device I2C EEPROM into a buffer allocated with kmalloc_obj(), which is sizeof(struct edge_ti_manuf_descriptor) = 10 bytes. The Size field comes from the device and is only validated (in check_i2c_image()) to make sure the descriptor fits within TI_MAX_I2C_SIZE (16384 bytes), not against the destination buffer size. A malicious USB device can therefore set Size to any value up to 16377, causing a heap overflow of up to 16367 bytes when plugged into a host running this driver. valid_csum() is called after read_rom() and also iterates buffer[0..Size-1], compounding the out-of-bounds access. Fix by rejecting descriptors with unexpected length before calling read_rom(). [ johan: amend commit message; also check for short descriptors ]

References

Community reviews

Loading reviews…