CVE-2026-80772 — HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler()
In the Linux kernel, the following vulnerability has been resolved: HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler() joycon_ctlr_read_handler() casts an incoming HID input report to struct joycon_input_report and parses it, guarding the cast only with a 12-byte length check: if (size >= 12) /* make sure it contains the input report */ joycon_parse_report(ctlr, (struct joycon_input_report *)data); struct joycon_input_report is 49 bytes: a 13-byte header followed by a union whose IMU arm is 36 bytes. For an IMU report joycon_parse_report() -> joycon_parse_imu_report() walks that union (struct offsets 13..48), so a report of exactly 12 bytes with data[0] == JC_INPUT_IMU_DATA passes the guard yet is read up to 37 bytes past its declared length. The over-read bytes are decoded into accelerometer/gyroscope values and forwarded to userspace through the "(IMU)" input device, leaking driver-internal memory. data[0] and size are fully controlled by a malicious or spoofed Joy-Con/Pro Controller. Receive buffers are sized to the maximum report length, so this is an over-read within the allocation rather than a slab OOB, but the decoded bytes still reach userspace. The sibling subcmd path in joycon_ctlr_handle_event() already bounds the same cast correctly: if (size < sizeof(struct joycon_input_report) || data[0] != JC_INPUT_SUBCMD_REPLY) break; Use the same sizeof(struct joycon_input_report) bound here.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ 2af16c1f846bd60240745bbd3afa13d5f040c61a and < 33ea29f8b6141f2d265de807e110a6435b355cb0≥ 2af16c1f846bd60240745bbd3afa13d5f040c61a and < bd397c4123a4bc084913d8c7fdb40ef94e9f8172≥ 2af16c1f846bd60240745bbd3afa13d5f040c61a and < addca61f9a23c0d20a387c2040e70479f54518e1≥ 2af16c1f846bd60240745bbd3afa13d5f040c61a and < 51cfd1adbe7a46bb08af162abb3ab3b6820e2d15≥ 2af16c1f846bd60240745bbd3afa13d5f040c61a and < d4cabd4089adb59cf7974915737c52cc47a9bb1b≥ 2af16c1f846bd60240745bbd3afa13d5f040c61a and < 34725ed4719da424113db8449fb5485aaf71a913≥ 2af16c1f846bd60240745bbd3afa13d5f040c61a and < 27b376b945c0aac46fcdfcc950b14a85b874b557version 5.16 | Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 27, 2026 · 12 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
9 on the record
- git.kernel.org/stable/c/34725ed4719da424113db8449fb5485aaf71a913
- git.kernel.org/stable/c/27b376b945c0aac46fcdfcc950b14a85b874b557
- git.kernel.org/stable/c/51cfd1adbe7a46bb08af162abb3ab3b6820e2d15
- git.kernel.org/stable/c/33ea29f8b6141f2d265de807e110a6435b355cb0
- git.kernel.org/stable/c/addca61f9a23c0d20a387c2040e70479f54518e1
- git.kernel.org/stable/c/d4cabd4089adb59cf7974915737c52cc47a9bb1b
- github.com/advisories/GHSA-4hx6-rx69-cj3h
- nvd.nist.gov/vuln/detail/CVE-2026-80772
- git.kernel.org/stable/c/bd397c4123a4bc084913d8c7fdb40ef94e9f8172
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 5h
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 5h
- Unknown CVE-2026-99214 drm/vc4: hdmi: Move packet RAM enable to PM runtime 5h
- Unknown CVE-2026-99213 vsock: treat TCP_CLOSING as once-established 5h
- Unknown CVE-2026-99212 net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure 5h
- Unknown CVE-2026-99211 netlink: reset skb headers before unicast and multicast filtering 5h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80772 is "HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.