Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 3cf0b3c243e56bc43be560617416c1d9f301f44c, 5.16, 5.18; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-2.

Low priority for now. Upgrade to Linux Linux 3cf0b3c243e56bc43be560617416c1d9f301f44c, 5.16, 5.18; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Oct 28, 2025
Updated
Oct 30, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-40071

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 920e849b7d23ced84c9d11e11e2449e34973cfb8, e83b4e1540469babeffcfd44a605cf8a61542598, 5.18affected
    • 48473802506d2d6151f59e0e764932b33b53cb3b and later · before 8fcc22d6b90304d8b7436e101562218ea3faf73baffected · git
    • 48473802506d2d6151f59e0e764932b33b53cb3b and later · before c36785f9de03df56ff9b8eca30fa681a12b2310daffected · git
    • 48473802506d2d6151f59e0e764932b33b53cb3b and later · before 5416e89b81b00443cb03c88df8da097ae091a141affected · git
    • 48473802506d2d6151f59e0e764932b33b53cb3b and later · before c5a2791a7f11939f05f95c01f0aec0c55bbf28d5affected · git
    • 48473802506d2d6151f59e0e764932b33b53cb3b and later · before 3cf0b3c243e56bc43be560617416c1d9f301f44caffected · git
    • 5.15.54 and later · before 5.16affected · semver
    • 5.17.6 and later · before 5.18affected · semver
    • before 5.18not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.57-16.12.57-1
Debian:14linuxbefore 6.17.6-16.17.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40069Oct 28, 2025 · drm/msm: Fix obj leak in VM_BIND error path
    31Monitor
  • ← EarlierCVE-2025-40070Oct 28, 2025 · pps: fix warning in pps_register_cdev when register device fail
    0Monitor
  • Later →CVE-2025-40072Oct 28, 2025 · fanotify: Validate the return value of mnt_ns_from_dentry() before dereferencing
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3cf0b3c243e56bc43be560617416c1d9f301f44cVendor (CNA)
Linux Linux5.16Vendor (CNA)
Linux Linux5.18Vendor (CNA)
Linux Linux5416e89b81b00443cb03c88df8da097ae091a141Vendor (CNA)
Linux Linux8fcc22d6b90304d8b7436e101562218ea3faf73bVendor (CNA)
Linux Linuxc36785f9de03df56ff9b8eca30fa681a12b2310dVendor (CNA)
Linux Linuxc5a2791a7f11939f05f95c01f0aec0c55bbf28d5Vendor (CNA)
azl3 kernel 6.6.104.2-4 on Azure Linux 3.06.6.112.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.12.57-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records