dbcve.org
Falcon LinuxOperating system · Asrmicro

CVE-2025-49483

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-01
Fix available
A fix is available. Upgrade to 1536 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 tr069 modules allows Resource Leak Exposure. This vulnerability is associated with program files tr069/tr069_uci.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 or Release vulnerability in the TR-069 (CWMP) module's tr069_uci.c file allows resource leaks on affected ASR180x and ASR190x platforms running Falcon_Linux, Kestrel, or Lapwing_Linux firmware versions before v1536. The vulnerability stems from failure to properly release system resources (likely memory, file handles, or network connections) during TR-069 UCI operations.

MitigationUpgrade firmware to v1536 or later. If upgrading is not immediately feasible, audit TR-069 module resource usage and implement proper cleanup routines in tr069_uci.c to ensure all allocated resources are released on error paths and module termination.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 firmware version
    Check the currently running firmware version on the device. This is typically found via 'cat /etc/version', 'uname -a', or a device-specific command like 'show version' or 'fw_printenv'. Compare the version number to the affected range.
    Affected if Firmware version is below 1536 (e.g., v1400, v1500, etc.)
  2. Confirm platform model
    Identify the exact hardware platform model. Check /proc/cpuinfo, 'cat /proc/device-tree/model', or use 'lsb_release -a' if available. The vulnerability specifically affects ASR180x and ASR190x series devices.
    Affected if Device is an ASR180x or ASR190x platform variant
  3. Verify TR-069/CWMP module is active
    Determine if the TR-069 (CWMP) client module is enabled and running on the device. Check for processes related to TR-069 (commonly named tr069, cwmp, acs, or similar). Inspect /etc/config/tr069 or /etc/config/cwmp if UCI configuration exists, or look for running daemons with 'ps | grep -i tr069'.
    Affected if TR-069/CWMP module is loaded and actively running on the device
  4. Inspect tr069_uci.c resource handling
    If you have access to the source or binary of the TR-069 module, examine the tr069_uci.c file for proper resource cleanup. Look for missing fclose(), free(), or network socket close calls in error paths and termination routines.
    Affected if The tr069_uci.c file present on the device lacks proper resource cleanup in error handling paths (requires source code or binary analysis)

A device is affected if it runs on ASR180x or ASR190x hardware with Falcon Linux, Kestrel, or Lapwing Linux firmware version below 1536, and has the TR-069/CWMP module 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 firmware to v1536 or later. If upgrading is not immediately feasible, audit TR-069 module resource usage and implement proper cleanup routines in tr069_uci.c to ensure all allocated resources are released on error paths and module termination.

Recommended fix Moderate confidence

v1536 (or any later stable release)

  1. Upgrade Falcon Linux to version 1536 or later
  2. Upgrade Kestrel to version 1536 or later
  3. Upgrade Lapwing Linux to version 1536 or later
  4. After upgrading, verify the tr069 module (tr069/tr069_uci.c) no longer exhibits resource leak behavior

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 / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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