CVE-2021-1071
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 Tegra kernel in Jetson AGX Xavier Series, Jetson Xavier NX, TX1, TX2, Nano and Nano 2GB, all L4T versions prior to r32.5, contains a vulnerability in the INA3221 driver in which improper access control may lead to unauthorized users gaining access to system power usage data, which may lead to 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 · high confidenceThe NVIDIA Tegra kernel in Jetson devices (AGX Xavier, Xavier NX, TX1, TX2, Nano) running L4T versions prior to r32.5 contains an improper access control vulnerability in the INA3221 power monitoring driver. This allows unauthorized users to read sensitive system power usage data through the driver interface, resulting in information disclosure.
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< r32.5CVSS 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
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 your Jetson device modelCheck /proc/cpuinfo or use the command 'cat /sys/firmware/devicetree/base/model' to confirm the device is one of: AGX Xavier, Xavier NX, TX1, TX2, or NanoAffected if The device model matches any of these four Jetson variants
-
Check your L4T versionRun 'head -n 1 /etc/nv_tegra_release' or check the contents of /etc/nv_tegra_release to determine the L4T release versionAffected if The L4T version is earlier than r32.5 (for example, r32.4, r32.3, r32.2, etc.)
-
Verify the INA3221 driver is presentCheck if the INA3221 power monitoring driver is loaded by running 'ls /sys/class/hwmon/' and looking for hwmon devices, or check 'lsmod' for ina3221 moduleAffected if The INA3221 driver hwmon interface exists on the system
-
Check driver file permissionsExamine permissions on the INA3221 hwmon interface (e.g., /sys/class/hwmon/hwmon*/device/power* files) using 'ls -la' to see if world-readable access existsAffected if Files under the INA3221 hwmon interface are readable by all users (permissions include 'r--r--r--' or similar)
A user is affected if they are running a Jetson device (AGX Xavier, Xavier NX, TX1, TX2, or Nano) with L4T version prior to r32.5 and the INA3221 driver is accessible without proper authorization controls.
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 dataUpgrade Jetson devices to L4T r32.5 or later, which implements proper access controls in the INA3221 driver to restrict power usage data to authorized users.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1071 — 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-1071 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