# CVE-2026-53195: USB: serial: io_ti: fix heap overflow in build_i2c_fw_hdr()

> A heap overflow in the Linux kernel's io_ti USB serial driver allows attackers to execute arbitrary code or escalate privileges via a malicious firmware image.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** BELL-CVE-2026-53195, DEBIAN-CVE-2026-53195, GHSA-397c-7vfx-vg4x, ROOT-OS-DEBIAN-11-CVE-2026-53195, ROOT-OS-DEBIAN-12-CVE-2026-53195, ROOT-OS-UBUNTU-2204-CVE-2026-53195, ROOT-OS-UBUNTU-2404-CVE-2026-53195, UBUNTU-CVE-2026-53195

## What is CVE-2026-53195?

CVE-2026-53195 is a high-severity memory corruption vulnerability in Linux kernel, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

USB: serial: io_ti: fix heap overflow in build_i2c_fw_hdr()

build_i2c_fw_hdr() allocates a fixed-size buffer of
(16*1024 - 512) + sizeof(struct ti_i2c_firmware_rec) bytes, then
copies le16_to_cpu(img_header->Length) bytes into it without
validating that Length fits within the available space after the
firmware record header.

img_header->Length is a __le16 from the firmware file and can be
up to 65535. check_fw_sanity() validates the total firmware size
but not img_header->Length specifically.

Fix by rejecting images where img_header->Length exceeds the
available destination space.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-53195?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-53195?

Apply the vendor's patch.

## Is CVE-2026-53195 being exploited?

There is no known exploitation of CVE-2026-53195 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53195 and fix it if it is affected.

What it is: CVE-2026-53195 is a high-severity memory corruption vulnerability in Linux kernel, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53195 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53195/ (Markdown: https://insights.sbomify.com/CVE-2026-53195/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53195
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53195
- OSV: https://osv.dev/vulnerability/CVE-2026-53195

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53195/
Summaries are generated and may contain mistakes; the official description above is the record.