tty: n_gsm: Don't block input queue by waiting MSC
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
920e849b7d23ced84c9d11e11e2449e34973cfb8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tty: n_gsm: Don't block input queue by waiting MSC
Currently gsm_queue() processes incoming frames and when opening a DLC channel it calls gsm_dlci_open() which calls gsm_modem_update(). If basic mode is used it calls gsm_modem_upd_via_msc() and it cannot block the input queue by waiting the response to come into the same input queue.
Instead allow sending Modem Status Command without waiting for remote end to respond. Define a new function gsm_modem_send_initial_msc() for this purpose. As MSC is only valid for basic encoding, it does not do anything for advanced or when convergence layer type 2 is used.
From the CVE record · Linux
The Linux kernel’s n_gsm driver can block its input queue while opening a DLC channel in basic mode because it waits for a Modem Status Command response on that same queue. This can prevent incoming frames from being processed. The input does not specify whether an attacker can trigger this remotely, whether authentication is needed, or whether user interaction is required.
Operators running the Linux kernel should check whether their kernel includes the affected n_gsm code; affected versions are not specified.