CVE-2025-27560
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 · uneditedLoop with unreachable exit condition ('infinite loop') for some Intel(R) Platform within Ring 0: Kernel may allow a denial of service. System software adversary with a privileged 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 kernel-level infinite loop vulnerability in Intel(R) platforms (Ring 0) allows a privileged local user to cause a denial of service by triggering an unreachable exit condition. The attack has low complexity, requires no user interaction, and results in complete system unavailability.
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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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.
-
Confirm Intel CPU usageRun 'lscpu | grep -i vendor' or check /proc/cpuinfo for GenuineIntel to verify Intel hardware is presentAffected if System does not contain Intel processors - the vulnerability does not apply
-
Check Intel microcode versionOn Linux, run 'dmesg | grep -i microcode' or check /proc/cpuinfo for the microcode version. Compare the installed version to Intel-recommended microcode updates for your CPU modelAffected if Microcode version is older than the latest Intel-provided update for your specific CPU model
-
Verify kernel version and patchesRun 'uname -r' to get kernel version. Check your distribution's security advisories for CVE-2025-27560 kernel patches. On RHEL/CentOS: 'rpm -q kernel'. On Debian/Ubuntu: 'dpkg -l | grep linux-image'Affected if Kernel version lacks the CVE-2025-27560 patch and is older than patched distributions
-
Audit privileged local usersCheck /etc/passwd for users with UID 0 (root) or privileged group memberships (wheel, sudo). Run 'getent group wheel' or 'getent group sudo'. Review 'sudoers' file for non-root users with elevated privilegesAffected if Untrusted or unauthorized users have privileged (root/wheel/sudo) access to the local system
A system is affected if it runs on Intel hardware and has an unpatched microcode version or kernel, combined with the presence of untrusted privileged local users who could trigger the infinite loop.
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 Intel-provided firmware/microcode updates or kernel patches when available. Until then, restrict local access to trusted privileged users only and monitor for system hang conditions.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27560 — 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-27560 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