dbcve.org
Falcon LinuxOperating system · Asrmicro

CVE-2025-49489

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 (con_mgr components) allows Resource Leak Exposure. This vulnerability is associated with program files con_mgr/dialer_task.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

Improper resource shutdown in the con_mgr dialer_task.C component causes resource leak exposure in ASR Falcon_Linux, Kestrel, and Lapwing_Linux devices. The vulnerability allows resource exhaustion due to improper cleanup of memory, file handles, or network connections in the dialer task, potentially leading to denial of service. The issue is fixed in version v1536 and later.

MitigationUpgrade ASR Falcon_Linux, Kestrel, and Lapwing_Linux to version v1536 or later to resolve the resource leak in the con_mgr 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 device model
    Determine if the device is an ASR Falcon_Linux, Kestrel, or Lapwing_Linux variant. Check the system firmware, boot log, or device identification registers for the model designation.
    Affected if Device is not one of these three models (Falcon_Linux, Kestrel, Lapwing_Linux)
  2. Check installed firmware version
    Retrieve the current firmware version from the device system information, typically via CLI command (such as 'show version' or 'fw_printenv'), boot banner, or /proc/version entry. Compare the numeric version against 1536.
    Affected if Installed version is a number less than 1536 (for example, 1400, 1500, 1535)
  3. Verify con_mgr component is active
    Check if the con_mgr component is running on the device, typically via process list (ps command) or module status check. Look for processes named con_mgr or dialer_task.
    Affected if con_mgr or dialer_task process is actively running on the device

A user is affected if they have a Falcon_Linux, Kestrel, or Lapwing_Linux device running a firmware version below 1536 with the con_mgr component enabled and active.

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 resolve the resource leak in the con_mgr component.

Recommended fix Moderate confidence

v1536

  1. Identify the currently installed version of Falcon Linux, Kestrel, or Lapwing Linux using the system package manager or version command
  2. Download or obtain the updated version v1536 or later from the official ASR Micro source (www.asrmicro.com)
  3. Back up critical system configurations and data before performing the upgrade
  4. Upgrade the system to version 1536 or later using the appropriate package installation method for the distribution
  5. Verify the upgraded version matches or exceeds v1536 using the system version command
  6. Restart the con_mgr service or the entire system to ensure the new version with the fixed resource management is loaded
  7. Confirm the vulnerability is remediated by checking that the con_mgr/dialer_task.C component is no longer exposing resource leaks

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

Fix this in Falcon Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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