CVE-2025-9912
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 · uneditedNokia SR Linux is vulnerable to a local privilege escalation vulnerability. Successful exploitation of this vulnerability may allow an authenticated user to execute arbitrary commands with superuser privilege.
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 confidenceNokia SR Linux contains a local privilege escalation vulnerability that allows an authenticated user to execute arbitrary commands with superuser (root) privileges. The vulnerability likely involves improper validation or bypass of privilege separation mechanisms, enabling a standard user to escalate to root access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:H
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.
-
Confirm Nokia SR Linux is runningRun 'show system information' or check /etc/os-release to identify the operating systemAffected if System is Nokia SR Linux and vendor patch for CVE-2025-9912 has not been applied
-
Determine the installed SR Linux versionExecute 'show version' and note the exact software version stringAffected if Running version does not have the CVE-2025-9912 fix applied (compare against vendor release notes when patch becomes available)
-
Identify existing user accountsRun 'show users' or check /etc/passwd for all configured accounts on the systemAffected if Standard non-root user accounts exist on the system
-
Verify privilege separation configurationReview role-based access control settings via 'show system aaa' or examine the configuration for user role assignmentsAffected if Standard users are assigned roles that permit command execution beyond their intended privilege level
-
Check for unauthorized command executionReview system logs and audit logs for any command executions by non-privileged users that indicate privilege escalation attemptsAffected if Logs show non-root users executing commands with elevated privileges
Environment is affected if running Nokia SR Linux without the CVE-2025-9912 patch, with standard user accounts present and potential for those users to gain root access.
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.
From vendor dataApply vendor-supplied patches for CVE-2025-9912 when available; until then, restrict administrative access to trusted personnel only and monitor for unusual command execution patterns.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9912 — 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-9912 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