dbcve.org
Linux KernelOperating system · Linux

CVE-2026-46127

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 5.10.258 / 5.15.209 or later.
See remediation →
57/100
Remediation priority · Elevated
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/ocrdma: Don't NULL deref uctx on errors in ocrdma_copy_pd_uresp() Sashiko points out that pd->uctx isn't initialized until late in the function so all these error flow references are NULL and will crash. Use the uctx that isn't NULL.

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

The code follows a pointer that is null, crashing the process. An attacker who can reliably trigger it turns the crash into a denial of service. The fix is checking for null before use and handling the failure path gracefully.

General guidance for the null pointer dereference 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:>= 3.5, < 5.10.258>= 5.11, < 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.10.258 / 5.15.209 / 6.1.175 or later
Fixed in 5.10.2585.15.2096.1.175
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 5.10.258, 5.15.209, 6.1.175, or 6.6.140 (depending on your current branch)

  1. 1. Identify the currently running Linux kernel version using 'uname -r'
  2. 2. Determine which version branch your kernel belongs to (e.g., 5.10.x, 5.15.x, 6.1.x, or 6.6.x)
  3. 3. For kernels in the 5.10.x branch (>= 3.5, < 5.10.258): upgrade to kernel version 5.10.258 or later
  4. 4. For kernels in the 5.11-5.15 branch (>= 5.11, < 5.15.209): upgrade to kernel version 5.15.209 or later
  5. 5. For kernels in the 5.16-6.1 branch (>= 5.16, < 6.1.175): upgrade to kernel version 6.1.175 or later
  6. 6. For kernels in the 6.2-6.6 branch (>= 6.2, < 6.6.140): upgrade to kernel version 6.6.140 or later
  7. 7. Alternatively, apply the upstream stable patch commit 27b6eb1f27fda9bdd5cae028e396758cdf525845 to your kernel source and rebuild
  8. 8. After upgrade/reboot, verify the fix is present by checking the ocrdma driver source for the corrected error handling logic
Caveat Kernel upgrades may require driver recompilation and could introduce compatibility changes with proprietary modules

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 $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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