CVE-2021-1108
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 Linux kernel distributions contain a vulnerability in FuSa Capture (VI/ISP), where integer underflow due to lack of input validation may lead to complete denial of service, partial integrity, and serious confidentiality loss for all processes in the system.
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 confidenceNVIDIA Linux kernel drivers for FuSa Capture (VI/ISP) contain an integer underflow vulnerability caused by insufficient input validation. This flaw in kernel-space code can be triggered to cause system-wide denial of service, compromise system integrity, and expose sensitive data across all processes.
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.1, < 32.6.1< 9.0CVSS 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
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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 the Jetson Linux versionRun 'cat /etc/nv_tegra_release' or check the kernel version with 'uname -r'Affected if The version is 32.1 or higher but below 32.6.1
-
Identify the Shield Experience versionOn NVIDIA Shield devices, check the system settings for the software version under 'About' or 'System updates'Affected if The version is below 9.0
-
Verify the VI/ISP kernel driver presenceCheck for loaded video input driver modules with 'lsmod | grep -i vi' or 'lsmod | grep -i isp', or check for related device nodes under /dev/video* or /dev/media*Affected if The VI (Video Input) or ISP (Image Signal Processor) kernel modules are loaded and the interface is accessible
-
Check for FuSa Capture interface accessInspect /dev entries for FuSa-related devices (typically exposed through the NVIDIA VI driver interface) or check if any user-space process is accessing the capture interfaceAffected if The FuSa Capture interface is exposed and accessible to processes
A user is affected if they are running Jetson Linux 32.1 through 32.6.0 or Shield Experience below 9.0, and the VI/ISP kernel driver with FuSa Capture interface is loaded and accessible on their system.
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 · scoped9.032.6.1
Apply NVIDIA's security patch for the FuSa Capture driver when available; until then, restrict access to the VI/ISP interface and monitor for exploitation attempts.
Jetson Linux 32.6.1 or later; Shield Experience 9.0 or later
- Identify the current Jetson Linux version by running 'cat /etc/nv_tegra_release' or checking the kernel version with 'uname -r'
- For Jetson Linux: Backup all critical data before proceeding with the upgrade
- For Jetson Linux: Update to Jetson Linux release 32.6.1 or later by following NVIDIA's standard upgrade procedures (typically via NVIDIA SDK Manager or OTA update mechanism)
- For Shield Experience: Update to Shield Experience version 9.0 or later through the system settings or OTA update
- After upgrade, verify the new version is installed: confirm Jetson Linux >= 32.6.1 or Shield Experience >= 9.0
- Reboot the system to ensure all changes take effect
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-2021-1108 — 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-1108 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