VulnerabilityPublished 19 Jul 2026

CVE-2026-63943: Linux kernel · Input: xpad – fix out-of-bounds access for Share button

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 30 Oct 2026, 15:48 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Linux Linux	Affected =6.6.91 =6.12.29 =6.14.7	Fixed in–

AI-suggested

A fix is available that corrects the offset calculation and adds bounds checking in the xpad input driver. Users should update to the patched Linux kernel versions to remediate this issue.

Description

A vulnerability in the Linux kernel's xpad input driver allows out-of-bounds memory access when processing the Share button input from certain game controllers. This occurs because the function xpadone_process_packet uses the packet length directly without sufficient bounds checking, potentially leading to invalid memory reads if a malformed packet with insufficient length is received. The issue has been fixed by adding proper offset calculations and bounds checks against the packet length.

Impact

The vulnerability allows a malformed input packet from a controller device to cause out-of-bounds memory access in the kernel. While the exact impact is not detailed, out-of-bounds access in kernel code can lead to system instability, crashes, or potentially privilege escalation if exploited. No known exploits in the wild have been reported.

Summary

The Linux kernel's xpad input driver had a flaw in the xpadone_process_packet() function where it used the urb->actual_length value directly to index into the data array for the Share button byte. Since both the length and data content are controlled by the device, a malicious or broken controller could send a GIP_CMD_INPUT packet with an actual_length less than 18 bytes, causing out-of-bounds access beyond the array. The vulnerability was addressed by recalculating the offset and adding bounds checks to ensure safe indexing within the packet length.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 15:48 UTC

Technical details

References

Community reviews

Related threats