Look up another CVE · open CVE-2025-40071 in the interactive tracker
CVE-2025-40071
tty: n_gsm: Don't block input queue by waiting MSC
Published 2025-10-28 (12 months ago) by the Linux kernel CNA. Subsystem drivers/tty. Debian urgency: not yet assigned.
Debian does not build this code. The per-release build detail is under "Where it lives" below.
What to do, per Debian release
Debian's own status for CVE-2025-40071 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixed | 6.12.57-1 | Update the kernel and reboot. Fixed in 6.12.57-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 6.17.6-1 | Update the kernel and reboot. Fixed in 6.17.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.17.6-1 | Update the kernel and reboot. Fixed in 6.17.6-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/tty/n_gsm.c
- What this is
- TTY LAYER AND SERIAL DRIVERSMAINTAINERS section matched on drivers/tty/ · linux-kernel@vger.kernel.org · Supported
- Kernel module
- none to look for. The file would have gone into n_gsm, and Debian does not compile it into that module, so finding n_gsm in lsmod would say nothing about this CVE.
Check it on the machine
grep -w CONFIG_N_GSM /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.
- bookworm, trixie, forky, sidn
- n
- not enabled on any flavour - this release does not build the code
- Build switch
- CONFIG_N_GSM
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2025-10-28 (12 months ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.20%, higher than 9.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/tty
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.18 | 6.6.112 | c36785f9de03 |
| 5.18 | 6.12.53 | 5416e89b81b0 |
| 5.18 | 6.17.3 | c5a2791a7f11 |
| 5.18 | 6.18 | 3cf0b3c243e5 |
| 5.15.54 | 0 | 0 |
| 5.17.6 | 0 | 0 |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2025-40071, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.