CVE-2021-1112
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 nvmap, where a null pointer dereference may lead to complete denial of service.
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's Linux kernel driver contains a null pointer dereference vulnerability in the nvmap component, which is part of their memory management subsystem. When the driver attempts to dereference a null pointer during normal operation, it causes a kernel panic resulting in complete system 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.1, < 32.6.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify NVIDIA Jetson hardwareRun 'cat /proc/device-tree/model' or check '/sys/firmware/devicetree/base/model' to confirm the system is NVIDIA Jetson hardwareAffected if The system is not NVIDIA Jetson hardware - not affected by this CVE
-
Check Jetson Linux versionExamine the version file typically found at '/etc/nv_tegra_release' or run 'uname -a' to get the kernel version stringAffected if Version is 32.1 or higher but lower than 32.6.1 - the system falls within the affected version range
-
Verify nvmap component presenceRun 'lsmod | grep nvmap' or check '/proc/modules' for the nvmap kernel module to confirm the memory management component is loadedAffected if nvmap module is loaded and version is in the affected range - the vulnerable component is active
-
Check for kernel panic indicatorsReview kernel logs using 'dmesg', 'journalctl -k', or '/var/log/kern.log' for kernel panic messages, oops errors, or unexpected rebootsAffected if Kernel panics or null pointer dereference errors appear in logs - indicates possible exploitation of this vulnerability
A system is affected if it is NVIDIA Jetson Linux running version 32.1 or higher but below 32.6.1, with the nvmap memory management component active, and is experiencing kernel panics.
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.6.1
Apply NVIDIA's kernel driver updates or patches for the nvmap component. Until patched, monitor for kernel panics and consider isolating affected systems to limit exposure to DoS conditions.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1112 — 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-1112 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