CVE-2025-40071

tty: n_gsm: Don't block input queue by waiting MSC

N/A

Published: October 28, 2025 at 11:48 AM UTC

Updated: October 19, 2026 at 09:10 PM 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

N/A

Exploit prediction

EPSS 0.2%

Description

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.

Affected

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

Linux Kernel · Linux

90%

5.15.54 ≤ v < 5.165.17.6 ≤ v < 5.1848473802506d2d6151f59e0e764932b33b53cb3b5.15.54 5.17.6 5.18920e849b7d23ced84c9d11e11e2449e34973cfb8e83b4e1540469babeffcfd44a605cf8a61542598

Vendor states this is fixed in 3cf0b3c243e56bc43be560617416c1d9f301f44c (fixed)

Vendor states this is fixed in 5416e89b81b00443cb03c88df8da097ae091a141 (fixed)

Vendor states this is fixed in c36785f9de03df56ff9b8eca30fa681a12b2310d (fixed)

Vendor states this is fixed in c5a2791a7f11939f05f95c01f0aec0c55bbf28d5 (fixed)

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

Vendor states this is fixed in 5.18 (unaffected)

Vendor states this is fixed in 6.12.53 (unaffected)

Vendor states this is fixed in 6.17.3 (unaffected)

Vendor states this is fixed in 6.18 (unaffected)

Vendor states this is fixed in 6.6.112 (unaffected)