Linux KernelOperating system · Linux
CVE-2026-53045
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn the Linux kernel, the following vulnerability has been resolved: memory: tegra124-emc: Fix dll_change check The code checking whether the specified memory timing enables DLL in the EMRS register was reversed. DLL is enabled if bit A0 is low. Fix the check.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn the Linux kernel's Tegra124 external memory controller (EMC) driver, the logic for checking whether DLL (Delay Locked Loop) is enabled in the EMRS register was reversed. The code incorrectly checked if bit A0 was high when DLL is actually enabled when bit A0 is low. This incorrect check could cause the driver to misconfigure memory timings, potentially leading to memory instability or data corruption on affected Tegra124 systems.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Linux KernelOperating system
>= 4.2, < 5.10.258>= 5.11, < 5.15.209>= 5.16, < 6.1.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the hardware platformCheck /sys/firmware/devicetree/base/compatible or run 'cat /proc/cpuinfo' to look for Tegra124 or NVIDIA Tegra124 referencesAffected if The system is NOT running on Tegra124 hardware - if not, the CVE does not apply
-
Check the kernel versionRun 'uname -r' to get the kernel versionAffected if The kernel version is older than the version containing the fix (no specific version provided, but compare to your kernel's release date)
-
Verify the EMC driver is presentCheck for the EMC driver module: 'ls /lib/modules/$(uname -r)/kernel/drivers/memory/tegra/ 2>/dev/null' or look for 'tegra124-emc' in /sys or module listAffected if The driver is not loaded or not present - the vulnerability only applies when this specific driver is in use
-
Check if the driver is actively usedRun 'lsmod | grep -i emc' or check /sys/class/memory/ for EMC device nodesAffected if The EMC driver is not loaded into memory - without the driver active, the flawed code is not executing
A system is affected only if it is running on Tegra124 hardware with the EMC driver loaded, using a kernel version prior to the fix that inverts the DLL bit check logic.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data5.10.2585.15.2096.1.175
This is a logic error in kernel code that requires patching the kernel with the corrected bit-check logic. No user-facing mitigation is available beyond kernel updates. The fix is a simple inversion of the DLL enable check from 'if (bit A0 is set)' to 'if (bit A0 is clear)'.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53045 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-53045 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data