CVE-2021-3493
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 · uneditedThe overlayfs implementation in the linux kernel did not properly validate with respect to user namespaces the setting of file capabilities on files in an underlying file system. Due to the combination of unprivileged user namespaces along with a patch carried in the Ubuntu kernel to allow unprivileged overlay mounts, an attacker could use this to gain elevated privileges.
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 overlayfs implementation in the Linux kernel did not properly validate file capabilities on files in underlying filesystems with respect to user namespaces. Combined with Ubuntu's patch allowing unprivileged overlay mounts, this allowed local attackers to gain elevated privileges through privilege escalation.
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< 18.04>= 18.04.1, < 20.04< 20.10CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Confirm the operating system is UbuntuRun: cat /etc/os-release and look for 'Ubuntu' in the NAME or ID fieldAffected if The system is not Ubuntu - this CVE specifically affects Ubuntu Linux kernels
-
Check the Ubuntu version against affected rangesRun: cat /etc/os-release and compare the VERSION_ID or VERSION string against: < 18.04; >= 18.04.1 and < 20.04; < 20.10. For example, 18.04.1 through 18.04.5 and 19.10 are affectedAffected if The installed Ubuntu version falls within any of the vulnerable ranges (< 18.04; >= 18.04.1 and < 20.04; < 20.10)
-
Verify if unprivileged user namespaces are enabledRun: sysctl kernel.unprivileged_userns_clone (if it exists) or check /proc/sys/kernel/unprivileged_userns_clone. Also check for any AppArmor or seccomp configurations that may restrict user namespace creationAffected if Unprivileged user namespaces are enabled (value is 1 or not restricted), which is required for the exploit chain to work
-
Check if overlayfs is accessible to the userAttempt to mount an overlayfs as an unprivileged user: mkdir -p /tmp/overlay_test && mount -t overlay overlay_test -o lowerdir=/tmp,upperdir=/tmp,workdir=/tmp /tmp/overlay_test 2>&1. Alternatively, check if the overlay kernel module is loaded (lsmod | grep overlay)Affected if Unprivileged users can mount overlay filesystems, which is part of Ubuntu's patch that enables this vulnerability
The system is affected if it is running a vulnerable Ubuntu version (within the specified ranges) AND unprivileged user namespaces are enabled AND unprivileged overlay mounts are possible.
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 · scoped18.0420.0420.10
Apply the Linux kernel security patch to address the improper capability validation in overlayfs; alternatively, consider disabling unprivileged user namespaces and unprivileged overlay mounts if not required by the environment.
Ubuntu 18.04: Upgrade to linux-image 5.4.0-1041 or later (HWE kernel); Ubuntu 20.04: Upgrade to linux-image 5.4.0-1041 or later; Ubuntu 20.10: Upgrade to linux-image 5.8.0-1044 or later
- Run 'sudo apt update' to refresh package lists
- Run 'sudo apt upgrade linux-image-generic' (or 'sudo apt-get update && sudo apt-get install linux-image-generic') to install the fixed kernel
- Reboot the system to load the updated kernel: 'sudo reboot'
- After reboot, verify the kernel version with 'uname -r' and confirm it's at or above the fixed version (e.g., 5.4.0-1041 for Ubuntu 18.04/20.04, 5.8.0-1044 for Ubuntu 20.10)
- Optionally, verify the fix is applied by checking that overlayfs does not allow unprivileged file capability changes
Generated from the published advisory — verify against the referenced sources before acting.
- 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-3493 — 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-3493 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