CVE-2025-5072
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 · uneditedResource leak vulnerability in ASR180x、ASR190x in con_mgr allows Resource Leak Exposure.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 confidenceA resource leak vulnerability exists in the con_mgr (connection manager) component of ASR180x and ASR190x hardware platforms running Falcon_Linux, Kestrel, or Lapwing_Linux firmware versions prior to v1536. The vulnerability allows resource leak exposure, likely due to improper cleanup of memory, file handles, or network connections within the connection manager.
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< 1536< 1536< 1536CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your hardware platformDetermine if the device is an ASR180x or ASR190x series platform by checking the system hardware identification or product documentationAffected if The hardware is an ASR180x or ASR190x platform
-
Identify the firmware variantCheck what firmware variant is installed on the device - look for Falcon_Linux, Kestrel, or Lapwing_Linux in the system firmware information or boot logsAffected if The firmware variant is Falcon_Linux, Kestrel, or Lapwing_Linux
-
Determine the firmware versionRetrieve the installed firmware version from the device system information, version command, or firmware metadataAffected if The firmware version is below 1536 (e.g., 1535, 1534, or earlier)
-
Verify con_mgr component presenceCheck if the con_mgr (connection manager) component is running or loaded on the system using process listings, module information, or component inventoryAffected if The con_mgr component is present and running on the device
You are affected if your device is an ASR180x or ASR190x running Falcon_Linux, Kestrel, or Lapwing_Linux firmware version below 1536 with the con_mgr component active.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1536
Upgrade affected ASR180x and ASR190x devices to Falcon_Linux, Kestrel, or Lapwing_Linux firmware version v1536 or later to patch the resource leak in con_mgr.
v1536 or later for Falcon Linux, Kestrel, or Lapwing Linux
- Identify the specific ASR180x or ASR190x device model running Falcon Linux, Kestrel, or Lapwing Linux
- Verify current firmware/software version is below v1536
- Obtain the v1536 or later firmware update from ASRMicro.com or official ASR distribution channels
- Follow the vendor's standard firmware upgrade procedure for the ASR180x/ASR190x platform
- Ensure the con_mgr component is updated as part of the v1536 upgrade
- Verify the upgrade was successful and confirm the new version is v1536 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5072 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5072 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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