media: streamzap: fix race between device disconnection and urb callback
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8e9e60640067858e8036d4d43bbf725c60613359 · < 4db62b60af2ccdea6ac5452fd20e29587ed85f57| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
media: streamzap: fix race between device disconnection and urb callback
Syzkaller has reported a general protection fault at function ir_raw_event_store_with_filter(). This crash is caused by a NULL pointer dereference of dev->raw pointer, even though it is checked for NULL in the same function, which means there is a race condition. It occurs due to the incorrect order of actions in the streamzap_disconnect() function: rc_unregister_device() is called before usb_kill_urb(). The dev->raw pointer is freed and set to NULL in rc_unregister_device(), and only after that usb_kill_urb() waits for in-progress requests to finish.
If rc_unregister_device() is called while streamzap_callback() handler is not finished, this can lead to accessing freed resources. Thus rc_unregister_device() should be called after usb_kill_urb().
Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
From the CVE record · Linux
A race between streamzap device disconnection and an in-progress USB callback can cause a NULL pointer dereference or access to freed resources, crashing the kernel. The input does not specify whether an attacker can trigger this over a network or locally, or whether authentication or user interaction is required.
Engineers running the Linux kernel with the streamzap driver should check their installations; affected versions are not specified.