CVE-2022-48836

Input: aiptek - properly check endpoint type

MEDIUM

5.5

CVSS Score

Published: July 16, 2024 at 12:25 PM UTC

Updated: June 17, 2026 at 05:16 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: Input: aiptek - properly check endpoint type Syzbot reported warning in usb_submit_urb() which is caused by wrong endpoint type. There was a check for the number of endpoints, but not for the type of endpoint. Fix it by replacing old desc.bNumEndpoints check with usb_find_common_endpoints() helper for finding endpoints Fail log: usb 5-1: BOGUS urb xfer, pipe 1 != type 3 WARNING: CPU: 2 PID: 48 at drivers/usb/core/urb.c:502 usb_submit_urb+0xed2/0x18a0 drivers/usb/core/urb.c:502 Modules linked in: CPU: 2 PID: 48 Comm: kworker/2:2 Not tainted 5.17.0-rc6-syzkaller-00226-g07ebd38a0da2 #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 Workqueue: usb_hub_wq hub_event ... Call Trace: <TASK> aiptek_open+0xd5/0x130 drivers/input/tablet/aiptek.c:830 input_open_device+0x1bb/0x320 drivers/input/input.c:629 kbd_connect+0xfe/0x160 drivers/tty/vt/keyboard.c:1593

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 3.12.53v ≥ 3.2.793.12.53 ≤ v < 3.133.2.79 ≤ v < 3.34.10 ≤ v < 4.14.2734.15 ≤ v < 4.19.2364.20 ≤ v < 5.4.1874.4 ≤ v < 4.14.2734.4 ≤ v < 4.19.2364.4 ≤ v < 4.9.3084.4 ≤ v < 5.10.1084.4 ≤ v < 5.15.314.4 ≤ v < 5.16.174.4 ≤ v < 5.174.4 ≤ v < 5.4.1875.11 ≤ v < 5.15.315.16 ≤ v < 5.16.175.5 ≤ v < 5.10.1083.12.53 3.2.79 4.48e20cf2bce122ce9262d6034ee5d5b76fbb92f9690eb3c037fe3f0f25f01713a92725a8daa2b41f3a7c0ba06670f99c252d5bb74258dddbf50fef837

Vendor states this is fixed in 35069e654bcab567ff8b9f0e68e1caf82c15dcd7 (fixed)

Vendor states this is fixed in 5600f6986628dde8881734090588474f54a540a8 (fixed)

Vendor states this is fixed in 57277a8b5d881e02051ba9d7f6cb3f915c229821 (fixed)

Vendor states this is fixed in 6de20111cd0bb7da9b2294073ba00c7d2a6c1c4f (fixed)

Vendor states this is fixed in e732b0412f8c603d1e998f3bff41b5e7d5c3914c (fixed)

Vendor states this is fixed in e762f57ff255af28236cd02ca9fc5c7e5a089d31 (fixed)

Vendor states this is fixed in f0d43d22d24182b94d7eb78a2bf6ae7e2b33204a (fixed)

Vendor states this is fixed in fc8033a55e2796d21e370260a784ac9fbb8305a6 (fixed)

Affected range stops below 3.13, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.3, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.14.273 (unaffected)

Vendor states this is fixed in 4.19.236 (unaffected)

Vendor states this is fixed in 4.4 (unaffected)

Vendor states this is fixed in 4.9.308 (unaffected)

Vendor states this is fixed in 5.10.108 (unaffected)

Vendor states this is fixed in 5.15.31 (unaffected)

Vendor states this is fixed in 5.16.17 (unaffected)

Vendor states this is fixed in 5.17 (unaffected)

Vendor states this is fixed in 5.4.187 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references