Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2026-53045

A bug in the Linux kernel’s memory timing logic for Nvidia Tegra124 devices has been fixed. The code that determines whether a DLL is enabled was reversed, potentially allowing an attacker to manipulate memory timings. The issue is now resolved in updated kernel releases.

publishedJun 24, 2026
last modifiedJul 21, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
41th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 20, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel users running the tegra124-emc memory controller, such as systems with Nvidia Tegra124 hardware. Any distribution that ships the affected kernel version is impacted.

02

Real-world impact

An attacker could exploit the incorrect DLL enable check to alter memory timings, leading to arbitrary code execution or privilege escalation on the affected system.

03

Why this severity

The CVSS score of 9.8 reflects that the flaw can be triggered over the network without authentication, gives the attacker full control over the system, and has no mitigations in place. The vulnerability allows complete compromise, hence the critical rating.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade the Linux kernel to a version that includes the fix for CVE-2026-53045.
  2. 02Reboot the system to load the updated kernel.

NVD-referenced vendor advisory

05

Timeline

  1. Jun 24, 2026 · Jun 24, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 21, 2026 · 13d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 21, 2026 · 13d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →