Bug 2493703 (CVE-2026-53315) - CVE-2026-53315 kernel: drm/amd/ras: Fix NULL deref in ras_core_get_utc_second_timestamp()
Summary: CVE-2026-53315 kernel: drm/amd/ras: Fix NULL deref in ras_core_get_utc_second...
Keywords:
Status: NEW
Alias: CVE-2026-53315
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-26 21:01 UTC by OSIDB Bzimport
Modified: 2026-06-29 17:45 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-06-26 21:01:43 UTC
In the Linux kernel, the following vulnerability has been resolved:

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

ras_core_get_utc_second_timestamp() retrieves the current UTC timestamp
(in seconds since the Unix epoch) through a platform-specific RAS system
callback and is used for timestamping RAS error events.

The function checks ras_core in the conditional statement before calling
the sys_fn callback. However, when the condition fails, the function
prints an error message using ras_core->dev.

If ras_core is NULL, this can lead to a potential NULL pointer
dereference when accessing ras_core->dev.

Add an early NULL check for ras_core at the beginning of the function
and return 0 when the pointer is not valid. This prevents the
dereference and makes the control flow clearer.

Comment 1 Mauro Matteo Cascella 2026-06-29 17:17:18 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026062621-CVE-2026-53315-f75d@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.