CVE-2026-64014

Description

A flaw was found in the Linux kernel's usbtouchscreen driver. A local attacker with a specially crafted USB touch screen device could exploit this vulnerability by sending a malicious interrupt packet with an oversized length field. This improper handling of input lengths can lead to an out-of-bounds read, allowing the attacker to leak sensitive kernel memory contents to userspace. In some scenarios, this could also result in a system crash.

Statement

An out of bounds read in the usbtouchscreen NEXIO parser occurs because data_len and x_len are taken from a device supplied packet header and were not bounded by the URB buffer size. A malicious or compromised USB touchscreen can advertise a length much larger than the 1024 byte transfer buffer, making nexio_read_data scan beyond packet data while looking for threshold crossings. The first matching bytes can influence ABS_X and ABS_Y input events, so adjacent kernel memory may be exposed to local userspace through reported touch coordinates, and a farther read can fault and crash the kernel. For the CVSS the PR:N because the attacker does not need an account on the target when they can control the attached USB device. The issue is not network reachable in normal deployments. Impact is confidentiality loss and denial of service, with no supported integrity or privilege escalation primitive from this patch context.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.27.1N/A
Attack VectorPhysicalLocalN/A
Attack ComplexityLowLowN/A
Privileges RequiredNoneLowN/A
User InteractionNoneNoneN/A
ScopeUnchangedUnchangedN/A
ConfidentialityLowHighN/A
Integrity ImpactNoneNoneN/A
Availability ImpactHighHighN/A

Vector

Red Hat: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)

An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.

Confidentiality

Technical Impact: Read Memory; Read Files or Directories

An attacker could read confidential data if they are able to control resource references.

Integrity,Confidentiality,Availability

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.

Frequently Asked Questions

Want to get errata notifications? Sign up here.