dbcve.org
Falcon LinuxOperating system · Asrmicro

CVE-2025-49490

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-01
Fix available
A fix is available. Upgrade to 1536 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Resource leak vulnerability in ASR180x in router allows Resource Leak Exposure. This vulnerability is associated with program files router/sms/sms.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

A resource leak vulnerability exists in the SMS handling module (router/sms/sms.c) of ASR180x router chips running Falcon_Linux, Kestrel, or Lapwing_Linux firmware versions before v1536. The vulnerability allows resource leak exposure, likely due to improper cleanup of memory, file handles, or buffers allocated during SMS processing operations.

MitigationUpgrade ASR180x-based router firmware to version v1536 or later, which contains the patched sms.c module with proper resource management and cleanup routines.

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
None
Integrity
None
Availability
Low

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

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 the router chipset
    Check the device specifications, boot logs, or /proc/cpuinfo for ASR180x or Asrmicro branding. Many ASR180x devices also expose chipset info via `cat /proc/arm_chip_id` or `dmesg | grep -i asr`.
    Affected if The device does not use an ASR180x chipset - if it is a different vendor's SoC, this CVE does not apply.
  2. Determine the firmware variant
    Check the firmware build information, boot logs, or /etc/version for one of the three affected Linux variants: Falcon_Linux, Kestrel, or Lapwing_Linux. Run `cat /proc/version` or inspect the kernel image string.
    Affected if The device runs a different firmware variant not listed in the affected products.
  3. Check the firmware version number
    Extract the firmware version from the device (often via `cat /proc/version`, `cat /etc/version`, `fw_printenv`, or the web UI). Compare it numerically to version 1536.
    Affected if The installed firmware version is less than 1536 (for example, 1400, 1500, or any version number below 1536).
  4. Verify SMS functionality is active
    Inspect if the SMS module (router/sms/sms.c) is loaded or enabled. Check for SMS-related processes via `ps | grep sms`, look for /sms/ paths in the filesystem (`ls /router/sms/`), or check if SMS-related services are running.
    Affected if SMS handling is compiled into the firmware and actively used - the vulnerability only exposes risk when SMS processing code is present and operational.

The device is affected if it uses an ASR180x chipset with Falcon_Linux, Kestrel, or Lapwing_Linux firmware below version 1536 and has SMS functionality enabled in the build.

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-based router firmware to version v1536 or later, which contains the patched sms.c module with proper resource management and cleanup routines.

Recommended fix Moderate confidence

v1536 or later

  1. Identify the specific ASR180x router device model and current firmware version
  2. Access the device management interface or use vendor-provided firmware update mechanism
  3. Obtain firmware version 1536 or later from ASR Micro (www.asrmicro.com) or authorized distribution channels
  4. Apply the firmware update following the vendor's standard upgrade procedure
  5. After reboot, verify the firmware version is now 1536 or higher to confirm the update was successful

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

Fix this in Falcon Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49490 — 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-49490 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