CVE-2026-72394 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, users of Linux kernel with aspeed-g6-pwm-tach driver, system administrators, and security teams responsible for Linux kernel-based systems should be aware of this vulnerability. They should review and apply patches, monitor system logs, and implement compensating controls to prevent exploitation. Additionally, operators and platform administrators should be informed about the potential impact on their systems and the necessary mitigation steps. Vulnerability management and security teams should prioritize patching and monitoring of affected systems. Those responsible for asset inventory and change management should also be notified to ensure proper tracking and remediation of exposed assets. This includes verifying system configurations, reviewing logs for potential exploitation attempts, and ensuring that compensating controls are in place where patches cannot be applied immediately. The vulnerability affects various Linux kernel deployments, making it essential for a broad range of stakeholders to take appropriate actions based on their specific environments and risk assessments. This includes verifying affected scope, reviewing vendor guidance, and planning for updates or mitigations through normal change control processes. Compensating controls, such as monitoring and detection, should be reviewed and enhanced where necessary to protect against potential exploitation. Overall, a coordinated approach involving multiple stakeholders is necessary to effectively manage and mitigate this vulnerability across different Linux kernel deployments and environments. Linux distributions and vendors should also be engaged to ensure that patches are integrated into their products and that guidance is provided to their users. By taking these steps, organizations can reduce the risk associated with this vulnerability and protect their Linux kernel-based systems from potential attacks. The vulnerability's impact on various Linux kernel versions and configurations should be carefully assessed, and appropriate measures should be taken to prevent exploitation. This includes reviewing system configurations, applying patches, and enhancing

Technical summary

The aspeed_tach_val_to_rpm() function in the aspeed-g6-pwm-tach driver does not check for a zero tachometer value before performing a division. This can lead to a divide-by-zero exception and kernel panic if the hardware reports a tachometer value of 0. The issue arises from the lack of a zero-value check, which can happen due to extremely fast pulses, stuck edges, or hardware glitches. Linux kernel developers and maintainers should review and apply patches to mitigate this vulnerability.

Defensive priority

Medium

Recommended defensive actions

• Review and apply the provided patches to the Linux kernel
• Monitor system logs for divide-by-zero exceptions
• Implement compensating controls to prevent exploitation
• Perform a thorough review of system configurations to identify potential vulnerabilities
• Verify that all necessary patches are applied and up-to-date
• Conduct regular security audits to detect and address potential issues
• Engage with Linux kernel developers and maintainers for guidance on mitigation strategies

Evidence notes

The vulnerability exists in the aspeed-g6-pwm-tach driver of the Linux kernel. The aspeed_tach_val_to_rpm() function calculates fan RPM using the tachometer value but does not check if the tachometer value is zero before performing the division. This can lead to a divide-by-zero exception and kernel panic if the hardware reports a tachometer value of 0.

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.