In the Linux kernel, the following vulnerability has been resolved: drm/amd/ras: Fix NULL deref in ras_core_get_utc_second_timestamp()… (CVE-2026-53315)
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.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's drm/amd/ras subsystem involves the function ras_core_get_utc_second_timestamp(), which retrieves the current UTC timestamp for RAS error event logging. The function conditionally checks the ras_core pointer before invoking a system callback, but if the pointer is NULL, it still attempts to access ras_core->dev to log an error message, leading to a NULL pointer dereference. This can cause a denial of service via kernel crash. The fix involves adding an early NULL check for ras_core and returning 0 if the pointer is invalid, preventing the dereference.
Potential Impact
This vulnerability can cause a denial of service by triggering a kernel NULL pointer dereference, resulting in a system crash or instability. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a patch is available, users should monitor vendor communications for updates. No specific workaround is provided in the available data.
In the Linux kernel, the following vulnerability has been resolved: drm/amd/ras: Fix NULL deref in ras_core_get_utc_second_timestamp()… (CVE-2026-53315)
Description
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.
CVSS v3.1
Score 5.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's drm/amd/ras subsystem involves the function ras_core_get_utc_second_timestamp(), which retrieves the current UTC timestamp for RAS error event logging. The function conditionally checks the ras_core pointer before invoking a system callback, but if the pointer is NULL, it still attempts to access ras_core->dev to log an error message, leading to a NULL pointer dereference. This can cause a denial of service via kernel crash. The fix involves adding an early NULL check for ras_core and returning 0 if the pointer is invalid, preventing the dereference.
Potential Impact
This vulnerability can cause a denial of service by triggering a kernel NULL pointer dereference, resulting in a system crash or instability. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a patch is available, users should monitor vendor communications for updates. No specific workaround is provided in the available data.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-43h2-vrg5-h3qp
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53315"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a4c33fd27e9c797195f284e
Added to database: 07/06/2026, 23:02:21 UTC
Last enriched: 07/06/2026, 23:09:36 UTC
Last updated: 07/31/2026, 19:24:49 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.