# drm/amd/ras: Fix NULL deref in ras_core_get_utc_second_timestamp()

CVE record · `CVE-2026-53315`

- **Identifiers:** `CVE-2026-53315`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 Jun 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Jun 2026, 19:41 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `13c91b5b4378b5d08dc9ae9121b1645a0beec0bb to before 6c84f7f0afc415691ffa7d48aa7ce1d8e6083032` (git)
  - affected: `13c91b5b4378b5d08dc9ae9121b1645a0beec0bb to before 2b8101cc3b34d4d80d799360d2744829d5964479` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.19`
  - unaffected: `before 6.19` (semver)
  - unaffected: `7.0.10 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's AMD RAS code (drm/amd/ras) can dereference a NULL pointer in ras_core_get_utc_second_timestamp() when ras_core is NULL, because the error path reads ras_core->dev. Version 6.19 is listed as affected, and the source gives few details on how an attacker could trigger the flaw. Upgrade to 7.0.10 or later in the 7.0 series, or to 7.1 or later. No workaround is listed.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0014, the 3rd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 26 Jun 2026, 19:41 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-53315)
- 26 Jun 2026, 20:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-53315)

## Sources

- [CVE List: CVE-2026-53315](https://www.cve.org/CVERecord?id=CVE-2026-53315)
- [NVD: CVE-2026-53315](https://nvd.nist.gov/vuln/detail/CVE-2026-53315)

### References from the CNA

- <https://git.kernel.org/stable/c/6c84f7f0afc415691ffa7d48aa7ce1d8e6083032>
- <https://git.kernel.org/stable/c/2b8101cc3b34d4d80d799360d2744829d5964479>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-53315>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-53315/>. Everything for agents: <https://agentprime.io/llms.txt>.
