USB: serial: mos7840: fix crash on resume
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d83b405383c965498923f3561c3321e2b5df5727 · < c15a688e49987385baa8804bf65d570e362f8576| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
USB: serial: mos7840: fix crash on resume
Since commit c49cfa917025 ("USB: serial: use generic method if no alternative is provided in usb serial layer"), USB serial core calls the generic resume implementation when the driver has not provided one.
This can trigger a crash on resume with mos7840 since support for multiple read URBs was added back in 2011. Specifically, both port read URBs are now submitted on resume for open ports, but the context pointer of the second URB is left set to the core rather than mos7840 port structure.
Fix this by implementing dedicated suspend and resume functions for mos7840.
Tested with Delock 87414 USB 2.0 to 4x serial adapter.
[ johan: analyse crash and rewrite commit message; set busy flag on resume; drop bulk-in check; drop unnecessary usb_kill_urb() ]
From the CVE record · Linux
The Linux kernel mos7840 USB serial driver can crash when a system resumes with affected ports open. The crash occurs because the second read request retains the wrong context pointer; the input does not specify an attacker path or authentication requirements.
Engineers running Linux kernels with the mos7840 USB serial driver should check their systems; affected versions are not specified.