CVE-2022-28194
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 · uneditedNVIDIA Jetson Linux Driver Package contains a vulnerability in the Cboot module tegrabl_cbo.c, where, if TFTP is enabled, a local attacker with elevated privileges can cause a memory buffer overflow, which may lead to code execution, loss of Integrity, limited denial of service, and some impact to confidentiality.
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 confidenceA buffer overflow vulnerability exists in the NVIDIA Jetson Linux Driver Package's Cboot module (tegrabl_cbo.c) that is triggerable when TFTP is enabled. A local attacker with elevated privileges can exploit this memory corruption to achieve code execution, compromise system integrity, cause limited denial of service, and partially impact confidentiality.
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< 32.7.2CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:L
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 Jetson device and Linux versionRun 'cat /etc/nv_tegra_release' or check the L4T version with 'dpkg -l | grep nvidia-l4t-core'Affected if The displayed version number is less than 32.7.2
-
Confirm Cboot is presentCheck for the Cboot binary or source files on the device filesystem, typically found in /boot or within the bootloader partitionAffected if Cboot (tegrabl_cbo.c module) is present and loadable on the system
-
Verify TFTP is enabled in Cboot configurationInspect the Cboot configuration files (commonly found in /boot/bootloader/ or the CBoot config) for TFTP-related settings such as 'enable_tftp' or 'tftp' optionsAffected if TFTP is explicitly enabled or configured in the Cboot settings
-
Check for TFTP boot environment variablesExamine boot configuration files or U-Boot environment for TFTP boot parameters (e.g., tftpboot, tftpaddr, bootfile variables)Affected if TFTP-related boot variables are set and active
A system is affected if it is a NVIDIA Jetson device running Jetson Linux version prior to 32.7.2 with TFTP functionality enabled in the Cboot configuration.
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.
dbcve · scoped32.7.2
Disable TFTP in the Cboot configuration if not required for deployment, and apply the NVIDIA firmware patch when released. Restrict local privileged access as a defense-in-depth measure.
32.7.2
- Upgrade Jetson Linux to version 32.7.2 or later from the NVIDIA Jetson Linux Driver Package
- Ensure the Cboot module is updated as part of the full system upgrade
- After upgrade, verify the TFTP configuration settings in the Cboot module are appropriate for your deployment
- Review release notes for version 32.7.2 to confirm all security patches are included
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28194 — 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-2022-28194 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