dbcve.org
Falcon LinuxOperating system · Asrmicro

CVE-2025-49492

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-01
Fix available
A fix is available. Upgrade to 1536 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Out-of-bounds write in ASR180x in lte-telephony, May cause a buffer underrun.  This vulnerability is associated with program files apps/atcmd_server/src/dev_api.C. This issue affects Falcon_Linux、Kestrel、Lapwing_Linux: before v1536.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Out-of-bounds write vulnerability (buffer underrun) in ASR180x LTE modem firmware's telephony component (atcmd_server/dev_api.C). The flaw allows writing before the allocated buffer boundary, potentially enabling remote code execution or denial of service in the cellular modem subsystem.

MitigationUpgrade ASR180x modem firmware to version v1536 or later for affected platforms (Falcon_Linux, Kestrel, Lapwing_Linux). This is a firmware-level fix requiring coordination with the modem vendor and device firmware update deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Falcon LinuxOperating system
Affected:< 1536
KestrelOperating system
Affected:< 1536
Lapwing LinuxOperating system
Affected:< 1536

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ASR180x modem presence
    Check system logs, modem diagnostic output, or /proc/ device information for ASR180x, Falcon, Kestrel, or Lapwing modem identifiers. On Linux hosts, 'lsusb' or 'mmcli -L' may list the modem. On embedded systems, check 'cat /proc/cpuinfo' or vendor-specific diagnostic interfaces.
    Affected if The system contains an ASR180x-series LTE modem (Falcon Linux, Kestrel, or Lapwing variants)
  2. Retrieve modem firmware version
    Send AT command '+CGMR' or 'AT+CGMR' to the modem via serial/USB AT interface, or query via modem management interface (e.g., 'mmcli -m 0' with ModemManager). The response displays the firmware build version string.
    Affected if Unable to retrieve firmware version indicates potential ASR180x modem with inaccessible firmware info
  3. Parse firmware version against affected range
    Compare the retrieved firmware version number/build to the vulnerable range. Extract numeric version from the build string (e.g., 'v1500', '1532', 'v1523'). Compare to threshold version 1536.
    Affected if Firmware version is below 1536 (e.g., 1535, 1500, 1400, or any build before v1536)
  4. Confirm telephony/atcmd_server component
    Review modem feature list or debug logs for presence of telephony services (AT command server, voice/RIL stack). Check if 'atcmd_server' or telephony-related AT commands are active. This may require vendor-specific diagnostic tools or modem debug logs.
    Affected if Telephony component (atcmd_server) is enabled and running on the ASR180x modem

System is affected if it contains an ASR180x LTE modem (Falcon Linux, Kestrel, or Lapwing) running firmware version below 1536 with the telephony/atcmd_server component enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1536 or later
Fixed in 1536
Interim mitigation

Upgrade ASR180x modem firmware to version v1536 or later for affected platforms (Falcon_Linux, Kestrel, Lapwing_Linux). This is a firmware-level fix requiring coordination with the modem vendor and device firmware update deployment.

Recommended fix High confidence

v1536 (or later) for Falcon Linux, Kestrel, and Lapwing Linux

  1. 1. Identify the current version of Falcon Linux, Kestrel, or Lapwing Linux running on the ASR180x device
  2. 2. Confirm the version is below 1536 (vulnerable)
  3. 3. Obtain the v1536 release or later from ASRMicro (www.asrmicro.com)
  4. 4. Follow ASRMicro's standard firmware upgrade procedure for the ASR180x platform
  5. 5. After upgrading, verify the new version is 1536 or higher
  6. 6. Test the lte-telephony functionality to ensure the upgrade did not introduce regressions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Falcon Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49492 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49492 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data