dbcve.org
Falcon LinuxOperating system · Asrmicro

CVE-2025-49481

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 ASR180x 、ASR190x in router modules allows Resource Leak Exposure. This vulnerability is associated with program files router/phonebook/pbwork-queue.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

This is a resource leak vulnerability in the pbwork-queue.C file within the router phonebook component of ASR180x and ASR190x router modules. The improper resource shutdown allows resources (likely memory or queue-related handles) to leak over time, potentially leading to denial of service or degraded performance in affected router firmware versions.

MitigationUpgrade Falcon_Linux, Kestrel, and Lapwing_Linux router firmware to version v1536 or later, which contains the fix for proper resource cleanup in the pbwork-queue 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 router model
    Check the router hardware model or system information to determine if it is an Asrmicro Falcon, Kestrel, or Lapwing device. This may be visible in the device label, boot logs, or via a command like 'cat /proc/cpuinfo' or 'show version'.
    Affected if The router is an Asrmicro Falcon, Kestrel, or Lapwing model.
  2. Determine installed firmware version
    Retrieve the current firmware version from the router. This is typically available via CLI commands such as 'show version', 'cat /etc/version', or through the web interface status page. Note the exact version number displayed.
    Affected if The firmware version cannot be determined or is not visible.
  3. Compare version against affected threshold
    Compare the installed firmware version number to 1536. The vulnerability affects versions strictly less than 1536 (versions 1 through 1535, including any subversions like 1535.1).
    Affected if The installed firmware version is less than 1536 (for example: 1535, 1500, 1200, etc.).
  4. Verify phonebook component presence
    Check if the pbwork-queue component is present and active on the system. This may involve inspecting running processes, loaded modules, or system logs related to the phonebook feature. Commands like 'ls -la /path/to/pbwork-queue' or checking system logs may reveal this.
    Affected if The pbwork-queue component is loaded, running, or accessible on the device.

The environment is affected if the router is an Asrmicro Falcon, Kestrel, or Lapwing device running firmware version lower than 1536, and the pbwork-queue phonebook component is in use.

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 Falcon_Linux, Kestrel, and Lapwing_Linux router firmware to version v1536 or later, which contains the fix for proper resource cleanup in the pbwork-queue component.

Recommended fix Moderate confidence

Falcon Linux v1536 / Kestrel v1536 / Lapwing Linux v1536

  1. Identify the specific ASR router module model (ASR180x or ASR190x) in your deployment
  2. Determine the current Linux distribution version running on the router (Falcon Linux, Kestrel, or Lapwing Linux)
  3. Backup current router configuration before performing any upgrade
  4. Upgrade the router's Linux firmware to version 1536 or later
  5. Verify the upgrade was successful and the router is functioning normally
  6. Confirm the resource leak vulnerability in pbwork-queue.C is resolved

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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