CVE-2026-89449 Linux CVE debrief

Who should care

Linux kernel developers, administrators, and security teams should review and apply the patch to fix the memory leak vulnerability. Affected Linux kernel deployments may be vulnerable to denial of service (DoS) attacks and system instability. Operators and platform teams should assess their exposure and plan for updates or mitigations.

Why it matters

A memory leak vulnerability was found in the Linux kernel's iommu_mock_device_add function. This vulnerability can cause system instability and potentially lead to denial of service (DoS) attacks. Linux kernel developers and administrators should review and apply the patch to fix the issue.

• Memory leak vulnerability can cause system instability
• Potential for denial of service (DoS) attacks
• Requires patching to prevent exploitation

Technical summary

The iommu_mock_device_add function in the Linux kernel has a memory leak vulnerability. When device_add fails, the error path only calls iommu_fwspec_free, leaving dev->iommu still allocated. This triggers a kmemleak report. The issue is resolved by calling dev_iommu_free instead of iommu_fwspec_free in the device_add failure path. The fix prevents potential denial of service (DoS) attacks and system instability caused by the memory leak. Linux kernel developers and administrators should review and apply the patch to fix the issue.

Defensive priority

Medium

Recommended defensive actions

• Review and apply the patch to fix the memory leak vulnerability
• Update Linux kernel to the latest version
• Monitor system for potential memory leaks
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The vulnerability was discovered through fuzzing with Syzkaller, which triggered a kmemleak report. The issue is caused by a memory leak in the iommu_mock_device_add function. The fix involves calling dev_iommu_free instead of iommu_fwspec_free in the device_add failure path. No affected product deployments were confirmed to exist in managed environments at the time of CVE record publication.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.