VulnerabilityPublished 15 Aug 2026Updated 9 Oct 2026

CVE-2026-72424: Linux kernel · rtc: msc313: fix NULL deref in shared IRQ handler at probe

Affects Linux kernelSource GCVE Database

Not known to be exploited · fixed in 7.0.0-1014.14~24.04.1 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.0.0-1014.14~24.04.1, 7.0.0-1017.17~24.04.1, 7.0.0-1016.16~24.04.1 +11

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-cg6j-2hpf-xr59

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected <7.0.0-38.38	Fixed in 7.0.0-38.38
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected <7.0.0-1017.17	Fixed in 7.0.0-1017.17
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected <7.0.0-1016.16	Fixed in 7.0.0-1016.16
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected <7.0.0-1008.9	Fixed in 7.0.0-1008.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied to affected Linux kernel versions. The vendor advisory confirms that this issue has been resolved. Users should update to the fixed kernel versions as provided by their distribution or vendor.

Description

A NULL pointer dereference vulnerability in the Linux kernel's rtc: msc313 driver was fixed. The issue occurs in the shared IRQ handler during device probe due to improper handling of the device context pointer, which can lead to a NULL dereference in interrupt context. This flaw was addressed by changing the IRQ handler to use a direct pointer instead of relying on a device lookup that could return NULL. Multiple specific Linux kernel versions are affected. A patch is available to resolve this issue.

Impact

This vulnerability can cause a NULL pointer dereference in interrupt context, which may lead to a kernel crash or denial of service. The issue arises from improper handling of shared IRQ lines during device probe. There is no indication of code execution or privilege escalation from the provided data. No known exploits in the wild have been reported.

Summary

The Linux kernel vulnerability CVE-2026-72424 involves a NULL pointer dereference in the rtc: msc313 driver's shared IRQ handler at probe time. The function msc313_rtc_probe() calls devm_request_irq() with IRQF_SHARED and uses &pdev->dev as the cookie, but platform_set_drvdata() is only called later after clock setup. Because of this, if another device on the shared IRQ line triggers the handler before platform_set_drvdata() is called, dev_get_drvdata() returns NULL, leading to a NULL dereference of priv->rtc_base in interrupt context. The fix passes the priv pointer directly as the cookie, removing the dependency on probe order and preventing the NULL dereference.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Oct 2026, 08:41 UTC

Technical details

References

Community reviews

Related threats