CVE-2024-22374

What it actually does

Insufficient control flow management in affected Intel Xeon processors allows an authenticated local user to trigger denial of service through local access.

Why it matters to the business

Organizations running workloads on vulnerable Intel Xeon processors risk unplanned system downtime and degraded performance from local attacks, increasing operational costs and disrupting critical computing tasks.

How an attack unfolds

An authenticated attacker with local access supplies crafted inputs that exploit weak control flow checks, exhausting processor resources or forcing a crash without needing elevated privileges.

How to fix it

Apply the latest microcode or firmware updates from Intel for affected Xeon processors. For skratchdot/object-path-set update to commit 2d67a714159c4099589b6661fa84e6d2adc31761.

How to confirm the fix worked

Verify processor microcode versions against Intel's security advisories and confirm the object-path-set package is at the fixed commit hash via package manager or git history.

Typical attack path

1. Obtain local authenticated access to a system with affected Intel Xeon processors
2. Execute code or commands that trigger the control flow management flaw
3. Cause resource exhaustion leading to denial of service

How to detect it

Review system logs for unexpected processor faults or crashes on Xeon hardware and check for unusual local process activity that correlates with service interruptions.

What your security team should do

• Prioritize patching affected systems within standard maintenance windows given low EPSS and no KEV status
• Audit local access controls to limit authenticated users on Xeon-based hosts
• Monitor for processor-related stability issues in logs