CVE-2025-40071
Last modified
CVE-2025-40071 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 48473802506d2d6151f59e0e764932b33b53cb3b, < c36785f9de03df56ff9b8eca30fa681a12b2310d; >= 48473802506d2d6151f59e0e764932b33b53cb3b, < 5416e89b81b00443cb03c88df8da097ae091a141; >= 48473802506d2d6151f59e0e764932b33b53cb3b, < c5a2791a7f11939f05f95c01f0aec0c55bbf28d5; >= 48473802506d2d6151f59e0e764932b33b53cb3b, < 3cf0b3c243e56bc43be560617416c1d9f301f44c; 920e849b7d23ced84c9d11e11e2449e34973cfb8; e83b4e1540469babeffcfd44a605cf8a61542598; >= 5.15.54, < 5.16; >= 5.17.6, < 5.18 |
| Linux | Linux | 5.18 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-40071?
How severe is CVE-2025-40071?
How do I fix CVE-2025-40071?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-40066In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40067In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-40068In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2025-40069In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-4007A vulnerability classified as critical was found in Tenda W1…8.8
- CVE-2025-40070In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40072In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40073In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40074In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2025-40075In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2025-40076In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40077In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2025-40071?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
