CVE-2025-27249
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 · uneditedUncontrolled resource consumption for some Gaudi software before version 1.21.0 within Ring 3: User Applications may allow a denial of service. System software adversary with an authenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
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 · high confidenceA local authenticated user can cause a denial of service in Intel Gaudi software versions prior to 1.21.0 due to uncontrolled resource consumption in Ring 3 user applications. The vulnerability has low attack complexity, requires no user interaction or special internal knowledge, and impacts system availability.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Identify Intel Gaudi software installationSearch the system for Intel Gaudi software components, drivers, or SDK packages. Common locations include /opt/intel, /usr/local/lib, or check installed packages via package manager (dpkg -l, rpm -qa, or similar). Look for packages containing 'gaudi', 'habana', or 'intel Gaudi' in the name.Affected if Intel Gaudi software is found on the system
-
Determine installed Gaudi software versionQuery the installed Gaudi software version using system package tools, version files, or the Gaudi management tools (such as hl-smi or habana_visible_devices). Check version information in installed packages, /opt/intel/gaudi/version files, or run 'hlsmi -v' if available.Affected if A version is returned that is less than 1.21.0 (e.g., 1.20.0, 1.19.0, etc.)
-
Confirm the software is active or runnableVerify the Gaudi software stack is operational by checking for running processes, loaded kernel modules (look for habana or gaudi modules via lsmod), or accessible device files (/dev/habana*).Affected if The software is installed, version is below 1.21.0, and the stack is in use or accessible to local users
The environment is affected if Intel Gaudi software version 1.21.0 or later is NOT installed and the software stack is accessible to local authenticated users.
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 · scopedUpgrade Gaudi software to version 1.21.0 or later to remediate the uncontrolled resource consumption vulnerability.
1.21.0
- Upgrade Intel Gaudi software to version 1.21.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27249 — 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-27249 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