CVE-2025-49488
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 · uneditedImproper Resource Shutdown or Release vulnerability in ASR180x 、ASR190x in router components allows Resource Leak Exposure. This vulnerability is associated with program files router/phonebook/pb.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 confidenceImproper resource shutdown vulnerability in the router phonebook component (router/phonebook/pb.c) of ASR180x and ASR190x routers running Falcon_Linux, Kestrel, or Lapwing_Linux firmware before v1536. The vulnerability allows resource leak exposure due to improper cleanup of resources in the phonebook functionality.
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 router modelCheck the device model label or system information to confirm it is an ASR180x or ASR190x series routerAffected if Router is an ASR180x or ASR190x variant
-
Check firmware versionAccess router admin interface or run 'version'/'cat /proc/version' command via SSH/telnet to retrieve the installed firmware versionAffected if Firmware version is below 1536 (e.g., 1535 or earlier)
-
Identify firmware branch nameCheck firmware build information or release notes to determine if the running firmware is based on Falcon_Linux, Kestrel, or Lapwing_LinuxAffected if Firmware branch is Falcon_Linux, Kestrel, or Lapwing_Linux and version < 1536
-
Verify phonebook component is presentCheck for the presence of /router/phonebook/pb.c or related phonebook binaries/config files in the firmware filesystem if accessibleAffected if Phonebook component (pb.c) exists in the firmware build
Router is affected if it is an ASR180x or ASR190x device running Falcon_Linux, Kestrel, or Lapwing_Linux firmware version below 1536 with the phonebook component present.
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 router firmware to version v1536 or later to address the resource leak in the phonebook component (pb.c).
Falcon Linux / Kestrel / Lapwing Linux v1536
- 1. Identify the current version of Falcon Linux, Kestrel, or Lapwing Linux installed on the ASR180x or ASR190x router device.
- 2. Confirm the current version is below 1536.
- 3. Obtain the v1536 or later update package from the official ASRMicro or device vendor distribution channel.
- 4. Follow the standard firmware/software update procedure for the specific router device, typically via web UI, CLI, or hardware programming interface.
- 5. After applying the update, verify the new version number is 1536 or higher.
- 6. Confirm the router/phonebook/pb.c component has been updated as part of the release.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49488 — 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-49488 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