dbcve.org
Linux KernelOperating system · Linux

CVE-2026-46112

HIGH · 7.8 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 5.15.209 / 6.1.175 or later.
See remediation →
80/100
Remediation priority · High
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
In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix unlocked call to hns_roce_qp_remove() Sashiko points out that hns_roce_qp_remove() requires the caller to hold locks. The error flow in hns_roce_create_qp_common() doesn't hold those locks for the error unwind so it risks corrupting memory. Grab the same locks the other two callers use.

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

Shared resources are accessed without correct locking, so concurrent operations interleave into inconsistent — and sometimes exploitable — states, or deadlock the service outright. These bugs are subtle and timing-dependent. The fix is correct, consistent locking or atomic operations around every shared resource.

General guidance for the improper locking 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:>= 4.17, < 5.15.209>= 5.16, < 6.1.175>= 6.2, < 6.6.140>= 6.7, < 6.12.88>= 6.13, < 6.18.30>= 6.19, < 7.0.7= 7.1

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

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 5.15.209 / 6.1.175 / 6.6.140 or later
Fixed in 5.15.2096.1.1756.6.140
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to Linux kernel 5.15.209+, 6.1.175+, 6.6.140+, or 6.12.88+ (depending on your release train)

  1. Identify your current Linux kernel version using `uname -r`
  2. Determine which kernel release series you are running (e.g., 5.15.x, 6.1.x, 6.6.x, 6.7.x, 6.12.x)
  3. Upgrade your Linux kernel to a version that includes the fix: for 5.15.x series upgrade to >= 5.15.209, for 6.1.x series upgrade to >= 6.1.175, for 6.6.x series upgrade to >= 6.6.140, or for 6.12.x series upgrade to >= 6.12.88
  4. If using a distribution kernel (e.g., Ubuntu, RHEL, Debian), check if a distribution-specific security update is available that includes this fix
  5. After kernel upgrade, reboot the system to load the patched kernel
  6. Verify the fix is applied by checking the kernel version and confirming the commit is included: `grep -r 0c99acbc8b6c /boot/` or checking kernel source
Caveat Kernel upgrades may require system reboot and could have compatibility implications with custom kernel modules; ensure critical modules are compatible with the new kernel version

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-2026-46112 — 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-2026-46112 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