CVE-2025-27249
📋 TL;DR
This vulnerability allows an authenticated local attacker to cause denial of service through uncontrolled resource consumption in Gaudi software. It affects systems running Gaudi software versions before 1.21.0. The attack requires local access but no special privileges or user interaction.
💻 Affected Systems
- Gaudi software
⚠️ Manual Verification Required
This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.
Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).
🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Complete system unavailability due to resource exhaustion, potentially affecting all services on the host
Likely Case
Degraded performance or temporary service interruption for Gaudi-dependent applications
If Mitigated
Minimal impact with proper resource limits and monitoring in place
🎯 Exploit Status
Attack requires authenticated user but is low complexity; local access needed
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 1.21.0
Vendor Advisory: https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01374.html
Restart Required: Yes
Instructions:
1. Download Gaudi software version 1.21.0 or later from Intel. 2. Stop Gaudi services. 3. Install the updated version. 4. Restart Gaudi services. 5. Verify the update was successful.
🔧 Temporary Workarounds
Implement resource limits
linuxSet resource quotas for Gaudi processes to limit potential DoS impact
# Use systemd resource controls: systemctl set-property gaudi.service MemoryLimit=2G CPUQuota=80%
# Use cgroups: cgcreate -g memory,cpu:gaudi_limit && cgset -r memory.limit_in_bytes=2G gaudi_limit && cgset -r cpu.cfs_quota_us=80000 gaudi_limit
Restrict user access
linuxLimit which users can run Gaudi applications to reduce attack surface
# Review and tighten sudoers: visudo
# Set strict file permissions: chmod 750 /opt/gaudi/bin/*
# Use mandatory access controls: setsebool -P gaudi_user_exec off
🧯 If You Can't Patch
- Implement strict access controls to limit which users can interact with Gaudi software
- Deploy monitoring and alerting for abnormal resource consumption by Gaudi processes
🔍 How to Verify
Check if Vulnerable:
Check Gaudi version: gaudi --version or check installed package versionCheck Version:
gaudi --version 2>/dev/null || dpkg -l | grep gaudi || rpm -qa | grep gaudiVerify Fix Applied:
Confirm version is 1.21.0 or later and test resource consumption under load📡 Detection & Monitoring
Log Indicators:
- Unusual memory or CPU consumption by Gaudi processes
- Multiple Gaudi process spawns in short time
- System logs showing resource exhaustion warnings
Network Indicators:
- None (local attack only)
SIEM Query:
source="system_logs" AND (process="gaudi" OR process="*gaudi*") AND (message="*memory*" OR message="*cpu*" OR message="*resource*")