CVE-2021-3760
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 · uneditedA flaw was found in the Linux kernel. A use-after-free vulnerability in the NFC stack can lead to a threat to confidentiality, integrity, and system availability.
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 confidenceA use-after-free vulnerability exists in the Linux kernel's NFC (Near Field Communication) subsystem. The flaw allows an attacker to potentially execute arbitrary code or cause a denial of service by freeing memory that is still being accessed, leading to corruption of heap memory and potential system compromise.
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>= 4.0, < 4.4.290>= 4.5, < 4.9.288>= 4.10, < 4.14.253>= 4.15, < 4.19.214>= 4.20, < 5.4.156>= 5.5, < 5.10.76>= 5.11, < 5.14.15= 34= 9.0all versionsall versionsall versionsall versionsall versionsCVSS 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.
-
Check the kernel versionRun 'uname -r' or 'cat /proc/version' to obtain the running kernel versionAffected if The kernel version falls within any of these ranges: >= 4.0 and < 4.4.290; >= 4.5 and < 4.9.288; >= 4.10 and < 4.14.253; >= 4.15 and < 4.19.214; >= 4.20 and < 5.4.156; >= 5.5 and < 5.10.76; >= 5.11 and < 5.14.15
-
Check if NFC subsystem is activeRun 'lsmod | grep -i nfc' to list loaded NFC kernel modules, or check for NFC device entries with 'ls -la /dev/nfc*' or 'cat /sys/class/nfc/'Affected if Any NFC modules are loaded or NFC devices are present in the system
-
Check if NFC kernel modules are availableList NFC modules in the kernel directory: 'ls /lib/modules/$(uname -r)/kernel/drivers/nfc/' or check kernel config with 'grep -i nfc /boot/config-$(uname -r)'Affected if NFC support is compiled as a module or built-in (CONFIG_NFC or related options enabled)
-
For NetApp systems, identify the model and firmware versionCheck the NetApp H-series model (H300s, H500s, H700s, H300e, or H500e) and obtain firmware version via the device management interface or 'nc admin' command if applicableAffected if The system is a NetApp H300s, H500s, H700s, H300e, or H500e device with any firmware version
The environment is affected if the kernel version is within any of the listed vulnerable ranges AND the NFC subsystem is enabled or available on the system, or if it is a NetApp H-series device.
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 · scoped4.4.2904.9.2884.14.253
Apply the kernel security patch for CVE-2021-3760 and update to a patched kernel version. If NFC is not required, consider disabling the NFC kernel module to reduce the attack surface until the patch can be applied.
Linux Kernel 4.4.290+ / 4.9.288+ / 4.14.253+ / 4.19.214+ depending on your kernel branch; or vendor-supplied kernel update for Debian 9.0 / Fedora 34
- Identify the current kernel version using 'uname -r'
- For Debian 9.0: Apply Debian Security Advisory DSA-XXXX (check security.debian.org for the specific advisory for this CVE) and upgrade kernel packages via 'apt update && apt upgrade linux-image-*'
- For Fedora 34: Apply Fedora updates via 'dnf update' to get the patched kernel
- For upstream Linux: Upgrade kernel to version 4.4.290 or newer, OR 4.9.288 or newer, OR 4.14.253 or newer, OR 4.19.214 or newer
- For H300s/H500s/H700s/H300e/H500e Firmware: Contact device vendor for firmware update; no vendor patch is currently available in the reference sources
- Reboot the system to load the patched kernel
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-3760 — 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-3760 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