CVE-2024-42277

What it actually does

NULL pointer dereference in sprd_iommu_cleanup when dom->sdev is NULL before invoking sprd_iommu_hw_en, causing kernel crash or memory corruption.

Why it matters to the business

Unexpected system crashes or denial of service on affected Linux devices using the sprd IOMMU driver, increasing downtime and operational risk across 1,393 downstream dependents until kernels are updated.

How an attack unfolds

An attacker with local access or the ability to trigger IOMMU cleanup paths (such as device removal or driver unload) causes the null dereference; no widespread in-the-wild exploitation is confirmed despite mentions in generic zero-day and Linux kernel campaigns.

How to fix it

Upgrade Linux kernel to version 5.15.165 or apply commit 8c79ceb4ecf823e6ec10fee6febb0fca3de79922; ensure all affected stable trees receive the fix.

How to confirm the fix worked

Verify running kernel version is at or above the fixed release; inspect source for the NULL check addition in sprd_iommu_cleanup before calling sprd_iommu_hw_en.

Typical attack path

1. Obtain local execution or trigger IOMMU device operations on a vulnerable kernel
2. Force execution of sprd_iommu_cleanup with dom->sdev set to NULL
3. Invoke sprd_iommu_hw_en resulting in NULL dereference and kernel fault

How to detect it

Search kernel logs and dmesg for sprd_iommu related NULL dereference oops or panic messages; correlate with device removal or driver unload events.

• sprd_iommu_cleanup
• sprd_iommu_hw_en
• dom->sdev

What your security team should do

• Apply kernel updates to 5.15.165 or newer immediately on all systems using sprd IOMMU
• Monitor for kernel oops reports involving sprd_iommu
• Prioritize patching on internet-facing or multi-tenant Linux deployments given ecosystem prevalence