Heimdall Security Logo

CVE-2026-80772

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 7.2.1, 6.1.185, <=6.1.*, 7.1.11, <=6.12.*, <34725ed4719da424113db8449fb5485aaf71a913, 5.16, 6.12.106, <51cfd1adbe7a46bb08af162abb3ab3b6820e2d15, <bd397c4123a4bc084913d8c7fdb40ef94e9f8172, 0, <=7.1.*, 6.6.154, <=6.6.*, <addca61f9a23c0d20a387c2040e70479f54518e1, <27b376b945c0aac46fcdfcc950b14a85b874b557, <5.16, <=6.18.*, <d4cabd4089adb59cf7974915737c52cc47a9bb1b, 6.18.47, <=7.2.*, <=*, <33ea29f8b6141f2d265de807e110a6435b355cb0, 2af16c1f846bd60240745bbd3afa13d5f040c61a, 7.3

Description

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.

Gravité et risque d'exploitation

CVE-2026-80772 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.21 %, ce qui la place devant 11.0 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 7.2.1, 6.1.185, <=6.1.*, 7.1.11, <=6.12.*, <34725ed4719da424113db8449fb5485aaf71a913, 5.16, 6.12.106, <51cfd1adbe7a46bb08af162abb3ab3b6820e2d15, <bd397c4123a4bc084913d8c7fdb40ef94e9f8172, 0, <=7.1.*, 6.6.154, <=6.6.*, <addca61f9a23c0d20a387c2040e70479f54518e1, <27b376b945c0aac46fcdfcc950b14a85b874b557, <5.16, <=6.18.*, <d4cabd4089adb59cf7974915737c52cc47a9bb1b, 6.18.47, <=7.2.*, <=*, <33ea29f8b6141f2d265de807e110a6435b355cb0, 2af16c1f846bd60240745bbd3afa13d5f040c61a, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE