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()… (CVE-2026-53195)
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.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel USB serial io_ti driver arises from a heap overflow in the build_i2c_fw_hdr() function. This function allocates a fixed-size buffer and copies a length of data specified by img_header->Length from the firmware image without ensuring that this length fits within the allocated buffer. Although the total firmware size is validated by check_fw_sanity(), the specific Length field is not checked, allowing an attacker to supply a malicious firmware image that triggers a heap overflow. The fix involves rejecting firmware images where img_header->Length exceeds the destination buffer size.
Potential Impact
Successful exploitation could lead to heap memory corruption, potentially allowing an attacker with limited privileges to execute arbitrary code, cause denial of service, or escalate privileges. The CVSS vector indicates local attack vector with low complexity, requiring low privileges, no user interaction, and results in high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description states a fix by rejecting oversized firmware images, but no explicit patch or update link is provided. Users should monitor Microsoft Security Response Center advisories for official patches or updates addressing this issue.
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()… (CVE-2026-53195)
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.
CVSS v3.1
Score 7.8high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel USB serial io_ti driver arises from a heap overflow in the build_i2c_fw_hdr() function. This function allocates a fixed-size buffer and copies a length of data specified by img_header->Length from the firmware image without ensuring that this length fits within the allocated buffer. Although the total firmware size is validated by check_fw_sanity(), the specific Length field is not checked, allowing an attacker to supply a malicious firmware image that triggers a heap overflow. The fix involves rejecting firmware images where img_header->Length exceeds the destination buffer size.
Potential Impact
Successful exploitation could lead to heap memory corruption, potentially allowing an attacker with limited privileges to execute arbitrary code, cause denial of service, or escalate privileges. The CVSS vector indicates local attack vector with low complexity, requiring low privileges, no user interaction, and results in high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description states a fix by rejecting oversized firmware images, but no explicit patch or update link is provided. Users should monitor Microsoft Security Response Center advisories for official patches or updates addressing this issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_vex
- Csaf Version
- 2.0
- Publisher
- Microsoft Security Response Center
- Advisory Id
- msrc_CVE-2026-53195
- Cve Count
- 1
- Additional Cves
- []
- Cvss Version
- 3.1
Threat ID: 6a42ed8527e9c79719953c86
Added to database: 06/29/2026, 22:11:17 UTC
Last enriched: 07/07/2026, 00:34:35 UTC
Last updated: 07/31/2026, 19:24:49 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.