CVE-2022-48836

Input: aiptek - properly check endpoint type

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

5.5

CVSS

Severity: Medium

CVSS 3.1 •

EPSS 0.05%

Affected: Linux Linux

References

Link	Tags
https://git.kernel.org/stable/c/57277a8b5d881e02051ba9d7f6cb3f915c229821	patch
https://git.kernel.org/stable/c/fc8033a55e2796d21e370260a784ac9fbb8305a6	patch
https://git.kernel.org/stable/c/6de20111cd0bb7da9b2294073ba00c7d2a6c1c4f	patch
https://git.kernel.org/stable/c/e732b0412f8c603d1e998f3bff41b5e7d5c3914c	patch
https://git.kernel.org/stable/c/f0d43d22d24182b94d7eb78a2bf6ae7e2b33204a	patch
https://git.kernel.org/stable/c/e762f57ff255af28236cd02ca9fc5c7e5a089d31	patch
https://git.kernel.org/stable/c/35069e654bcab567ff8b9f0e68e1caf82c15dcd7	patch
https://git.kernel.org/stable/c/5600f6986628dde8881734090588474f54a540a8	patch

Frequently Asked Questions

What is the severity of CVE-2022-48836?: CVE-2022-48836 has been scored as a medium severity vulnerability.
How to fix CVE-2022-48836?: To fix CVE-2022-48836, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-48836 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2022-48836 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-48836?: CVE-2022-48836 affects Linux Linux, Linux Linux.