CVE-2024-41064

What it actually does

Race condition in powerpc EEH error reporting path where concurrent PCI device removal can mutate edev->pdev during access, leading to invalid memory dereference and kernel crash.

Why it matters to the business

Unexpected system crashes and downtime on PowerPC Linux systems during PCI hotplug or removal events under error conditions; low prevalence but affects kernel stability in affected environments.

How an attack unfolds

An attacker with local access or ability to trigger PCI device removal events can race eeh_pe_report_edev() to cause a NULL or invalid pointer dereference; listed threat actors in espionage and financial campaigns have targeted similar Linux kernel race conditions for denial of service or further exploitation.

How to fix it

Apply the upstream fix from commit 8836e1bf5838ac6c08760e0a2dd7cf6410aa7ff3 or upgrade to a Linux kernel stable branch containing this commit; hold the PCI rescan/remove lock during pdev copy.

How to confirm the fix worked

Verify presence of the referenced commit in the running kernel source; test concurrent PCI removal during simulated EEH events to confirm absence of crash; monitor kernel logs for resolved EEH oops patterns.

Typical attack path

1. Gain local execution or control over PCI device lifecycle events
2. Trigger EEH error reporting path concurrently with PCI remove/rescan
3. Cause edev->pdev to change without lock protection
4. Trigger kernel panic via invalid bus pointer access

How to detect it

Search kernel logs and crash dumps for oops or panic messages referencing eeh_pe_report_edev, powerpc EEH, or PCI remove races; correlate with PCI hotplug events in dmesg or syslog.

• eeh_pe_report_edev
• edev->pdev
• powerpc/eeh
• PCI rescan/remove lock

What your security team should do

• Prioritize kernel upgrade on all PowerPC systems within 30 days
• Review PCI hotplug and error handling configurations for exposure
• Enable enhanced kernel panic logging and monitoring for EEH events