Menu

Star on GitHub · 3.2k

CVE-2026-72424

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 &pd…

Published Aug 15, 2026EPSS 0.21%

Overview

CVE-2026-72424 is a known-severity vulnerability. It was published on August 15, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-72424?

CVE-2026-72424 is a known-severity vulnerability. It was published on August 15, 2026.

How severe is CVE-2026-72424?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-72424?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-72424?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-72424 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.