dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53336

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 6.6.143 / 6.12.94 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available 7 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: nvmem: layouts: onie-tlv: fix hang on unknown types The EEPROM on my board has a vendor specific entry of type 0x41. When stumbling upon that, this driver hangs in an endless loop. Fix it by keep incrementing the offset on unknown entries, so the loop will eventually stop.

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 confidence

The ONIE TLV nvmem layout driver in the Linux kernel enters an infinite loop when parsing EEPROM entries with unknown vendor-specific type codes (e.g., 0x41). The driver fails to advance the parsing offset when encountering unrecognized types, causing it to repeatedly process the same entry indefinitely.

MitigationApply the kernel patch that adds offset increment for unknown TLV entry types, or update to a kernel version containing this fix. For workarounds, avoid reading from EEPROMs with unknown vendor-specific entries until the kernel is patched.

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.4, < 6.6.143>= 6.7, < 6.12.94>= 6.13, < 6.18.36>= 6.19, < 7.0.13= 7.1

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 kernel version
    Run 'uname -r' or 'cat /proc/version' to get the running kernel version
    Affected if The kernel version falls within any of these ranges: >= 6.4 and < 6.6.143, >= 6.7 and < 6.12.94, >= 6.13 and < 6.18.36, >= 6.19 and < 7.0.13, or equals 7.1
  2. Verify ONIE TLV driver presence
    Check if the kernel was built with ONIE TLV support by looking for the driver file at /sys/bus/nvmem/devices/ or running 'ls -la /sys/class/nvmem/' to list NVMEM devices
    Affected if NVMEM devices exist on the system and the kernel version is in the affected range
  3. Identify ONIE-based hardware
    Look for network switches or embedded systems that use Open Network Install Environment (ONIE). Check dmesg for 'onie' or 'nvmem' related messages, or inspect /dev for nvmem device nodes
    Affected if The system is an ONIE-based network switch or embedded device with EEPROM storage that uses the ONIE TLV parser
  4. Check for TLV parsing in kernel logs
    Run 'dmesg | grep -i tlv' or 'dmesg | grep -i nvmem' to look for any messages related to TLV parsing or EEPROM reads
    Affected if The system attempts to parse ONIE TLV data from EEPROM and the kernel is in the affected version range

A system is affected if it runs a Linux kernel version in the affected ranges AND uses the ONIE TLV nvmem driver to parse EEPROM data from ONIE-based hardware such as network switches.

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.6.143 / 6.12.94 / 6.18.36 or later
Fixed in 6.6.1436.12.946.18.36
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch that adds offset increment for unknown TLV entry types, or update to a kernel version containing this fix. For workarounds, avoid reading from EEPROMs with unknown vendor-specific entries until the kernel is patched.

Recommended fix Moderate confidence

6.6.143, 6.12.94, 6.18.36, or 7.0.13 (depending on your current kernel branch)

  1. Upgrade the Linux kernel to version 6.6.143 or later if currently on 6.4.x - 6.6.x
  2. Upgrade the Linux kernel to version 6.12.94 or later if currently on 6.7.x - 6.12.x
  3. Upgrade the Linux kernel to version 6.18.36 or later if currently on 6.13.x - 6.18.x
  4. Upgrade the Linux kernel to version 7.0.13 or later if currently on 6.19.x - 7.0.x
  5. Alternatively, apply the upstream kernel patch which modifies the onie-tlv parser to increment the offset on unknown TLV types, allowing the parsing loop to terminate rather than hanging

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

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53336 — 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-53336 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