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

> A NULL pointer dereference in the Linux kernel RTC driver can cause a system crash when a shared IRQ is triggered during device probe.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72424, DEBIAN-CVE-2026-72424, GHSA-cg6j-2hpf-xr59, UBUNTU-CVE-2026-72424

## What is CVE-2026-72424?

CVE-2026-72424 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-72424?


## How do I fix CVE-2026-72424?

Apply the vendor's patch.

## Is CVE-2026-72424 being exploited?

There is no known exploitation of CVE-2026-72424 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72424 and fix it if it is affected.

What it is: CVE-2026-72424 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72424 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72424/ (Markdown: https://insights.sbomify.com/CVE-2026-72424/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72424
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72424
- OSV: https://osv.dev/vulnerability/CVE-2026-72424

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72424/
Summaries are generated and may contain mistakes; the official description above is the record.