dbcve.org
Linux KernelOperating system · Linux

CVE-2022-1652

HIGH · 7.8 CVSS v3.1 Published 2022-06-02
Fix available
A fix is available. Upgrade to 4.9.316 / 4.14.281 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Linux Kernel could allow a local attacker to execute arbitrary code on the system, caused by a concurrency use-after-free flaw in the bad_flp_intr function. By executing a specially-crafted program, an attacker could exploit this vulnerability to execute arbitrary code or cause a denial of service condition on 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 confidence

A concurrency use-after-free vulnerability exists in the Linux Kernel's bad_flp_intr function. An attacker can exploit this by executing a specially-crafted program that triggers the race condition, allowing arbitrary code execution or denial of service.

MitigationApply the relevant Linux kernel security patch when available. Until patched, limit local access to trusted users only, as this vulnerability requires local access to exploit.

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
Linux KernelOperating system
Affected:>= 2.6.12, < 4.9.316>= 4.10, < 4.14.281>= 4.15, < 4.19.245>= 4.20, < 5.4.196>= 5.5, < 5.10.118>= 5.11, < 5.15.42>= 5.16, < 5.17.10
Enterprise LinuxOperating system
Affected:= 9.0
Debian LinuxOperating system
Affected:= 10.0
H410c FirmwareOperating system
Affected:all versions
H300s FirmwareOperating system
Affected:all versions
H500s FirmwareOperating system
Affected:all versions
H700s FirmwareOperating system
Affected:all versions
H410s FirmwareOperating system
Affected:all versions

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check the Linux kernel version
    Run 'uname -r' to get the running kernel version, or check /proc/version
    Affected if The kernel version falls within any of these ranges: >= 2.6.12 and < 4.9.316; >= 4.10 and < 4.14.281; >= 4.15 and < 4.19.245; >= 4.20 and < 5.4.196; >= 5.5 and < 5.10.118; >= 5.11 and < 5.15.42; >= 5.16 and < 5.17.10
  2. Check if running Red Hat Enterprise Linux 9.0
    Check /etc/redhat-release or run 'hostnamectl' to identify the OS version
    Affected if The system is RHEL version 9.0
  3. Check if running Debian Linux 10.0
    Check /etc/debian_version or run 'lsb_release -a' to identify the OS version
    Affected if The system is Debian version 10.0
  4. Check Netapp H-series firmware version
    For H410c, H300s, H500s, H700s, or H410s, use the Netapp hardware management interface or run 'system firmware show' via ONTAP CLI to get firmware version
    Affected if The system is any of these Netapp models: H410c, H300s, H500s, H700s, or H410s (all firmware versions are affected)

The environment is affected if running a Linux kernel within the specified version ranges, or if running RHEL 9.0, Debian 10.0, or any of the listed Netapp H-series models.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.9.316 / 4.14.281 / 4.19.245 or later
Fixed in 4.9.3164.14.2814.19.245
Interim mitigation

Apply the relevant Linux kernel security patch when available. Until patched, limit local access to trusted users only, as this vulnerability requires local access to exploit.

Recommended fix High confidence

Linux Kernel 5.4.196 or later (LTS), or 4.19.245/4.14.281/4.9.316 depending on the branch in use

  1. 1. Identify the current running kernel version using 'uname -r'
  2. 2. For Enterprise Linux systems, update via 'yum update kernel' or 'dnf update kernel' and reboot
  3. 3. For Debian systems, update via 'apt-get update && apt-get upgrade linux-image' and reboot
  4. 4. For embedded/firmware devices (H300s, H410c, H410s, H500s, H700s), contact the device vendor for firmware updates addressing CVE-2022-1652
Caveat Kernel upgrades may require rebooting the system and could have compatibility implications with custom kernel modules or specific hardware drivers

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

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1652 — 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-2022-1652 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