CVE-2026-74397 Linux CVE debrief

Who should care

Linux kernel maintainers, developers, and users who need to assess exposure and apply patches to prevent potential transport domain leaks. Affected operator, platform, vulnerability-management, and security-team impact should be considered. Exposure in Linux kernel deployments should be assessed, and the patch or fix provided by the Linux kernel maintainers should be applied.

Why it matters

A vulnerability in the Linux kernel has been resolved, involving a transport domain rollback and initialization of the lb mutex. Linux kernel maintainers, developers, and users should assess exposure and apply patches.

• Verify the patch or fix has been applied to prevent potential transport domain leaks.
• Assess exposure in Linux kernel deployments and prioritize patching.
• Review Linux kernel patch notes and official CVE record for specific details on the vulnerability.

Technical summary

The vulnerability involves a transport domain rollback and initialization of the lb mutex in the Linux kernel. Specifically, mlx5_ib_alloc_transport_domain() allocates a transport domain and then may fail in mlx5_ib_enable_lb(), potentially leaking the allocated transport domain. Linux kernel maintainers, developers, and users should assess exposure and apply patches to prevent potential transport domain leaks. The patch or fix should be verified to prevent potential transport domain leaks. Affected versions and exposure in Linux kernel deployments should be assessed.

Defensive priority

Low

Recommended defensive actions

• Review the Linux kernel patch notes and official CVE record for specific details on the vulnerability.
• Verify the affected versions and assess exposure in your Linux kernel deployments.
• Apply the patch or fix provided by the Linux kernel maintainers.
• Verify 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 CVE record and NVD entry provide details on the vulnerability. However, the impact and affected versions require verification from the supplied official sources. The Linux kernel patch notes and official CVE record should be reviewed for specific details on the vulnerability. Affected versions and exposure in Linux kernel deployments should be assessed, and the patch or fix provided by the Linux kernel maintainers should be applied.

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.