CyberRota Analysis
AI-GeneratedA vulnerability exists in the Linux kernel's handling of shared IRQs within the msc313 RTC driver, where a NULL dereference can occur if another device triggers the interrupt before the driver data is set. This flaw can lead to potential system crashes or instability when the interrupt handler is invoked. Linux system administrators and developers utilizing the msc313 RTC driver should prioritize applying the fix to prevent exploitation and ensure system reliability.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: rtc: msc313: fix NULL deref in shared IRQ handler at probe msc313_rtc_probe() calls devm_request_irq() with IRQF_SHARED and &pdev->dev as the cookie, but platform_set_drvdata() is only called later after the clock setup. With a shared IRQ line, another device on the same line can trigger the handler in that window. The handler does dev_get_drvdata() on the cookie, gets NULL, and dereferences priv->rtc_base in interrupt context. Pass priv as the cookie directly so the handler reads it from dev_id without the lookup, removing the dependency on probe order.