VulnerabilityPublished 19 Jul 2026

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

Source GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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.

ghsa-p7rq-pjmq-p6gw

What to do

AI-suggested

A fix has been implemented in the Linux kernel to address this vulnerability by adding proper bounds checking in the xpad driver. Users should apply the official kernel updates that include this patch. Since this is a kernel-level fix, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed here; check the vendor or Linux kernel advisory for the exact fixed versions and update instructions.

Description

A vulnerability in the Linux kernel's xpad driver allowed out-of-bounds memory access when processing input packets from the Share button. This occurred because the function xpadone_process_packet() used the packet length directly from the device without proper bounds checking, enabling a malformed packet with insufficient length to cause invalid memory access. The issue has been fixed by adding proper offset calculation and bounds checking against the packet length.

Impact

The vulnerability allows a device-controlled input packet to cause out-of-bounds memory access in kernel space, which may lead to memory corruption or kernel crashes. There is no evidence of known exploits in the wild. The impact is limited to systems using the vulnerable xpad driver in the Linux kernel and receiving crafted input from a malicious or faulty device.

Summary

The Linux kernel xpad driver had a vulnerability (CVE-2026-63943) where the function xpadone_process_packet() used the actual_length field from a USB request block (urb) directly to index into the data array for the Share button. Since both the length and data are controlled by the device, a malicious or broken controller could send a packet with actual_length less than 18 bytes, causing out-of-bounds access beyond the data array. This could lead to memory corruption or kernel instability. The fix involved calculating the offset properly and verifying that the packet length is sufficient before accessing the data array.

References

Community reviews

Loading reviews…