Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-40071tty: n_gsm: Don't block input queue by waiting MSC

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 months later

    Published

  3. · 12 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 48473802506d2d6151f59e0e764932b33b53cb3b – < 8fcc22d6b90304d8b7436e101562218ea3faf73b
    • affected 48473802506d2d6151f59e0e764932b33b53cb3b – < c36785f9de03df56ff9b8eca30fa681a12b2310d
    • affected 48473802506d2d6151f59e0e764932b33b53cb3b – < 5416e89b81b00443cb03c88df8da097ae091a141
    • affected 48473802506d2d6151f59e0e764932b33b53cb3b – < c5a2791a7f11939f05f95c01f0aec0c55bbf28d5
    • affected 48473802506d2d6151f59e0e764932b33b53cb3b – < 3cf0b3c243e56bc43be560617416c1d9f301f44c
    • affected 920e849b7d23ced84c9d11e11e2449e34973cfb8
    • affected e83b4e1540469babeffcfd44a605cf8a61542598
    • affected 5.15.54 – < 5.16
    • affected 5.17.6 – < 5.18
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.112 – ≤ 6.6.*
    • unaffected 6.12.53 – ≤ 6.12.*
    • unaffected 6.17.3 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-40071 badge
[![CVE-2025-40071](https://cveledger.app/badge/CVE-2025-40071.svg)](https://cveledger.app/cve/CVE-2025-40071)

Record last updated .