dbcve.org
Linux KernelOperating system · Linux

CVE-2021-3653

HIGH · 8.8 CVSS v3.1 Published 2021-09-29
Fix available
A fix is available. Upgrade to 4.4.282 / 4.9.281 or later.
See remediation →
90/100
Remediation priority · Urgent
Public exploit Zero-click Patch available

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 · unedited
A flaw was found in the KVM's AMD code for supporting SVM nested virtualization. The flaw occurs when processing the VMCB (virtual machine control block) provided by the L1 guest to spawn/handle a nested guest (L2). Due to improper validation of the "int_ctl" field, this issue could allow a malicious L1 to enable AVIC support (Advanced Virtual Interrupt Controller) for the L2 guest. As a result, the L2 guest would be allowed to read/write physical pages of the host, resulting in a crash of the entire system, leak of sensitive data or potential guest-to-host escape. This flaw affects Linux kernel versions prior to 5.14-rc7.

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
How this class of weakness works · CWE-862

The application checks who you are but not whether you're allowed to perform a given action, so any authenticated user can reach things meant for others. This is the classic “change the ID in the URL” bug. The fix is an authorization check on every request, evaluated against the acting user's permissions.

General guidance for the missing authorization class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Linux KernelOperating system
Affected:>= 2.6.30, < 4.4.282>= 4.5, < 4.9.281>= 4.10, < 4.14.245>= 4.15, < 4.19.205>= 4.20, < 5.4.142>= 5.5, < 5.10.60>= 5.11, < 5.13.12= 5.14
Enterprise LinuxOperating system
Affected:= 7.0
Debian LinuxOperating system
Affected:= 9.0

CVSS 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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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 · scoped
Upgrade available Upgrade to 4.4.282 / 4.9.281 / 4.14.245 or later
Fixed in 4.4.2824.9.2814.14.245
Vendor patch bugzilla.redhat.com →
Recommended fix High confidence

Linux kernel >= 4.4.282, >= 4.9.281, >= 4.14.245, >= 4.19.205, or >= 5.14-rc7 (or vendor equivalent)

  1. 1. Identify the current running kernel version using 'uname -r' or 'cat /proc/version'
  2. 2. For RHEL/CentOS 7 systems: Update kernel package via 'yum update kernel' or 'dnf update kernel' and reboot to the new kernel
  3. 3. For Debian 9 systems: Update kernel via 'apt-get update && apt-get upgrade linux-image-amd64' and reboot
  4. 4. For upstream Linux kernels: Upgrade to one of the fixed versions: 4.4.282+, 4.9.281+, 4.14.245+, 4.19.205+, or 5.14-rc7+
  5. 5. After upgrade, verify the running kernel is no longer vulnerable using 'grep -i avic /sys/module/kvm_amd/parameters/avic' or checking /proc/cpuinfo for 'svm' features
Caveat Kernel upgrade requires system reboot; ensure compatibility of custom modules/services with new kernel before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-3653 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-3653 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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