dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53044

HIGH · 7.1 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.18.33 / 7.0.10 or later.
See remediation →
73/100
Remediation priority · Elevated
Zero-click 8 weeks old

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 · unedited
In the Linux kernel, the following vulnerability has been resolved: soc/tegra: cbb: Fix incorrect ARRAY_SIZE in fabric lookup tables Fix incorrect ARRAY_SIZE usage in fabric lookup tables which could cause out-of-bounds access during target timeout lookup.

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 · moderate confidence

In the Linux kernel's NVIDIA Tegra soc/cca driver, incorrect ARRAY_SIZE usage on fabric lookup tables allows out-of-bounds array access during target timeout lookups, potentially leading to memory corruption or information disclosure.

MitigationApply the kernel patch to correct the ARRAY_SIZE usage in the fabric lookup tables, ensuring array bounds are properly validated before lookup operations.

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
Affected:>= 6.17, < 6.18.33>= 6.19, < 7.0.10

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed kernel version
    Run 'uname -r' or check '/proc/version' to get the running kernel version
    Affected if The kernel version is >= 6.17 and < 6.18.33, OR >= 6.19 and < 7.0.10
  2. Identify NVIDIA Tegra hardware presence
    Check for Tegra SoC by examining '/proc/device-tree/compatible' or running 'lspci' for NVIDIA graphics, or check '/proc/cpuinfo' for Tegra identifiers
    Affected if The system contains NVIDIA Tegra System-on-Chip hardware
  3. Verify soc/cca driver is loaded
    Check for the CCA driver module by running 'lsmod | grep -i tegra' or searching for 'tegra' in '/proc/modules', or check driver presence in '/sys/module/'
    Affected if The NVIDIA Tegra soc/cca driver is present or loaded on the system
  4. Check driver source for vulnerable code pattern
    If the kernel source is available, locate the Tegra CCA driver (typically under drivers/soc/tegra/) and inspect fabric lookup table code for ARRAY_SIZE usage on lookup tables
    Affected if The driver source contains lookup tables used during target timeout lookups without proper bounds validation

A system is affected if it runs a vulnerable kernel version (6.17-6.18.32, 6.19-7.0.9) AND uses NVIDIA Tegra hardware with the soc/cca driver loaded, allowing out-of-bounds array access during fabric timeout lookups.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 6.18.33 / 7.0.10 or later
Fixed in 6.18.337.0.10
Interim mitigation

Apply the kernel patch to correct the ARRAY_SIZE usage in the fabric lookup tables, ensuring array bounds are properly validated before lookup operations.

Recommended fix High confidence

Kernel 6.18.33 (for 6.18.y branch) or 7.0.10 (for 6.19.y/7.0.y branch)

  1. Check current kernel version using 'uname -r' or 'cat /proc/version'
  2. If running kernel >= 6.17 and < 6.18.33, upgrade to kernel 6.18.33 or later
  3. If running kernel >= 6.19 and < 7.0.10, upgrade to kernel 7.0.10 or later
  4. After upgrade, reboot the system to load the fixed kernel
  5. Verify the fix by checking that the kernel version matches a fixed release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53044 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53044 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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