CVE-2026-72124 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, CAN isotp users and administrators, operators, platform, vulnerability-management, and security-team impact. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed and review compensating controls for exposed systems while remediation is scheduled and verified. They should check relevant monitoring, detection, and logs for exposed assets that need extra review and track exceptions, retest remediated assets, and close the item only after evidence is documented. They should confirm whether affected product deployments exist in managed environments and assign an owner for follow-up. They should also review the patch provided by the Linux kernel maintainers and update CAN isotp configurations.

Technical summary

The Linux kernel's CAN isotp has a vulnerability that allows for potential corruption of unrelated transfers due to a race condition in the TX state machine. The fix involves serializing TX state transitions under the so->rx_lock. This vulnerability affects Linux kernel developers and maintainers, CAN isotp users and administrators. The TX state machine was driven from multiple contexts, leading to potential corruption of unrelated transfers. The fix involves serializing TX state transitions under the so->rx_lock.

Defensive priority

Medium

Recommended defensive actions

• Apply the patch provided by the Linux kernel maintainers
• Review and update CAN isotp configurations
• Monitor for potential exploitation attempts
• 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
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD detail provide information on the vulnerability. However, the source detail is limited, and further verification is needed to confirm the affected scope and vendor remediation. Linux kernel developers and maintainers should verify the patch provided and review CAN isotp configurations. Users and administrators of CAN isotp should monitor for potential exploitation attempts and review compensating controls. The CVE record and NVD detail provide information on the vulnerability, but additional verification is needed to confirm the affected scope and vendor remediation.

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.