dbcve.org
Falcon LinuxOperating system · Asrmicro

CVE-2025-49491

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
Improper Resource Shutdown or Release vulnerability in ASR Falcon_Linux、Kestrel、Lapwing_Linux on Linux (traffic_stat modules) allows Resource Leak Exposure. This vulnerability is associated with program files traffic_stat/traffic_service/traffic_service.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 · high confidence

This is a resource leak vulnerability in the traffic_stat/traffic_service component (traffic_service.C) on Linux for ASR Falcon_Linux, Kestrel, and Lapwing_Linux devices. The vulnerability stems from improper resource shutdown or release in the traffic_stat modules, where system resources (such as memory, file handles, or network connections) are not properly cleaned up during operation, potentially leading to resource exhaustion over time.

MitigationUpgrade ASR Falcon_Linux, Kestrel, and Lapwing_Linux to version v1536 or later to obtain the patch that properly implements resource cleanup in the traffic_stat/traffic_service component.

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 ASR device model
    Check the device model or product name through system information, boot logs, or /proc/cpuinfo (look for 'Falcon', 'Kestrel', or 'Lapwing' identifiers)
    Affected if The device is an ASR Falcon_Linux, Kestrel, or Lapwing_Linux model
  2. Determine the installed firmware/software version
    Retrieve the OS version using 'uname -a', 'cat /etc/version', or vendor-specific tools (e.g., 'asr-version' if available)
    Affected if The reported version number is below 1536 (e.g., 1535, 1500, etc.)
  3. Verify the traffic_stat/traffic_service component is active
    Check running processes for traffic_service, traffic_stat, or related daemons using 'ps aux | grep -i traffic' or inspect /proc/modules for loaded traffic-related kernel modules
    Affected if The traffic_stat or traffic_service component is loaded or running on the device
  4. Confirm version is within vulnerable range
    Compare the identified version against the affected ranges: Falcon Linux < 1536, Kestrel < 1536, or Lapwing Linux < 1536
    Affected if The device is an affected ASR product AND the version is less than 1536 AND the traffic_stat/traffic_service component is present

The environment is affected if the device runs ASR Falcon_Linux, Kestrel, or Lapwing_Linux with a version below 1536 and has the traffic_stat/traffic_service 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 ASR Falcon_Linux, Kestrel, and Lapwing_Linux to version v1536 or later to obtain the patch that properly implements resource cleanup in the traffic_stat/traffic_service component.

Recommended fix High confidence

version 1536 or later

  1. 1. Identify the current version of the installed ASR product (Falcon Linux, Kestrel, or Lapwing Linux) using system inventory or version check command
  2. 2. Backup all existing configurations, especially those related to traffic_stat modules
  3. 3. Obtain the fixed version (v1536 or later) from ASR Micro's official distribution channel or support portal
  4. 4. Apply the upgrade following ASR Micro's standard upgrade procedure for the specific product
  5. 5. After upgrade, verify the traffic_service/traffic_service.C module is updated and running correctly
  6. 6. Confirm the vulnerability is resolved by checking the new version number

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-49491 — 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-49491 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