Linux KernelOperating system · Linux
CVE-2022-1786
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 use-after-free flaw was found in the Linux kernel’s io_uring subsystem in the way a user sets up a ring with IORING_SETUP_IOPOLL with more than one task completing submissions on this ring. This flaw allows a local user to crash or escalate their privileges 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 · high confidenceA use-after-free vulnerability in the Linux kernel's io_uring subsystem allows local privilege escalation when a ring is configured with IORING_SETUP_IOPOLL and multiple tasks complete submissions on that ring simultaneously.
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
>= 5.10, < 5.12all 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 Linux kernel versionRun `uname -r` or `cat /proc/version` to obtain the kernel version stringAffected if The kernel version is 5.10.x or 5.11.x (any patch level within >= 5.10, < 5.12)
-
Check if io_uring subsystem is in useLook for processes using io_uring by examining /proc/*/fd for io_uring ring file descriptors, or check application configurations that utilize io_uringAffected if Any application or process on the system is actively using io_uring
-
Determine if IORING_SETUP_IOPOLL is enabled for any io_uring ringInspect application source code or configuration for the IORING_SETUP_IOPOLL flag when initializing io_uring rings, or monitor system calls using `strace` to look for io_uring_setup with this flagAffected if Any io_uring ring on the system is configured with IORING_SETUP_IOPOLL
-
Assess multi-task access to io_uring ringsReview application architecture to determine if multiple tasks or threads submit and complete operations on the same io_uring ring concurrentlyAffected if More than one task simultaneously performs submissions and completions on an IOPOLL-configured ring
-
For NetApp H-series devices, identify the firmware versionUse the NetApp hardware management interface or run `sysctl` commands provided by NetApp to retrieve the firmware version of H300s, H410c, H410s, H500s, or H700s nodesAffected if The device is a NetApp H300s, H410c, H410s, H500s, or H700s with any firmware version (all versions affected)
You are affected if running a Linux kernel between 5.10 and 5.12 (exclusive) with an io_uring ring configured using IORING_SETUP_IOPOLL accessed by multiple concurrent tasks, or if using a NetApp H-series device with any firmware version.
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 data5.12
Apply the relevant kernel security patch or upgrade to a patched kernel version; this typically requires system reboot.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1786 — 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-2022-1786 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