CVE-2021-34375
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 · uneditedTrusty contains a vulnerability in all trusted applications (TAs) where the stack cookie was not randomized, which might result in stack-based buffer overflow, leading to denial of service, escalation of privileges, and information disclosure.
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 confidenceTrusty trusted applications have a vulnerability where the stack cookie (canary) is not randomized during compilation. This means stack-based buffer overflows cannot be detected at runtime, potentially allowing attackers to overwrite return addresses and achieve code execution, privilege escalation, or cause denial of service.
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.5.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 if the system is Nvidia Jetson LinuxCheck the system hardware and OS information. On Jetson devices, you can run 'cat /proc/device-tree/model' or check '/etc/nv_tegra_release' to confirm the device type.Affected if The system is not a Jetson Linux device - this CVE only affects Nvidia Jetson Linux.
-
Determine the installed Jetson Linux versionCheck the L4T (Linux for Tegra) version by running 'cat /etc/nv_tegra_release' or checking the kernel version with 'uname -a'. The version number after 'R' (for example, R32.x) corresponds to the Jetson Linux release.Affected if The version is earlier than 32.5.1 (for example, R32.4.x or earlier). Versions prior to 32.5.1 are affected by this vulnerability.
-
Verify if Trusty trusted applications are in useCheck if Trusty TEE (Trusted Execution Environment) is enabled on the system. Look for Trusty-related processes, services, or configuration files. On Jetson, this can be verified by examining the kernel configuration or checking for Trusty-related daemons.Affected if Trusty trusted applications are running on the system. If Trusty is not being used, the vulnerability in Trusty code does not apply.
-
Inspect the Trusty trusted application build configurationReview the build configuration or compilation flags used for the Trusty trusted applications on the device. Check if -fstack-protector-strong or similar stack protection flags are present in the build scripts or Makefiles.Affected if The Trusty applications were compiled without stack canary randomization (stack protector flags not enabled in the build). This is the vulnerable condition.
A system is affected if it is running Nvidia Jetson Linux version earlier than 32.5.1 AND uses Trusty trusted applications that were compiled without stack canary randomization enabled.
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 data32.5.1
Enable stack protector/canary compilation flags (e.g., -fstack-protector-strong) for all Trusty trusted applications and ensure stack canary randomization is enabled in the Trusted Application build process.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34375 — 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-2021-34375 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