LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46127: RDMA/ocrdma: Don't NULL deref uctx on errors in ocrdma_copy_pd_uresp()

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel reliability vulnerability in the ocrdma RDMA driver. The documented impact is a NULL pointer dereference on certain error paths, which can crash the kernel. The source bundle does not provide CVSS, confirmed exploitation, or a broader impact claim. Business urgency depends on whether affected systems load or use this RDMA driver.

Executive priority

Handle through normal kernel vulnerability management unless RDMA workloads or ocrdma usage are confirmed. Escalate priority for production systems where a kernel crash would materially affect service availability. Current evidence does not support emergency action based on exploitation.

Technical view

In RDMA/ocrdma, ocrdma_copy_pd_uresp() references pd->uctx during error handling before pd->uctx is initialized. That can dereference NULL and crash. The upstream fix changes those error paths to use the already available non-NULL uctx. The CVE lists Linux kernel affected versions and multiple stable commit references.

Likely exposure

Exposure is most likely on Linux systems with affected kernel builds where the ocrdma RDMA driver is present and reachable. Systems without this driver, without relevant RDMA hardware, or running fixed vendor kernels are less likely exposed. The provided data does not define remote, local, or privilege requirements.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. It describes a crash condition in error handling, not a full exploit chain. Treat this as a potential availability issue until vendor advisories or distribution-specific severity guidance provide more detail.

Researcher notes

Evidence is limited to the CVE record and kernel stable commit references. No CVSS, CWE, exploitability conditions, or distribution-specific advisories are included. The affected-version listing appears broad, so validation should rely on vendor kernel status and whether the ocrdma code path exists in deployed builds.

Mitigation direction

  • Check Linux vendor advisories for fixed kernel packages covering CVE-2026-46127.
  • Update affected kernels to versions containing the referenced stable fixes.
  • Prioritize systems using RDMA or the ocrdma driver.
  • If updates are delayed, assess whether ocrdma is needed on exposed systems.
  • Monitor distribution security notices for CVSS and operational guidance.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Check whether the ocrdma driver is built, installed, or loaded.
  • Map running kernels against vendor-fixed releases or referenced stable commits.
  • Confirm RDMA-capable hosts receive priority review.
  • Record exceptions where ocrdma is absent or not usable.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-46127 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfe2caefcdf5869f308c102e3d64d40683bfad711, fe2caefcdf5869f308c102e3d64d40683bfad711, fe2caefcdf5869f308c102e3d64d40683bfad711, fe2caefcdf5869f308c102e3d64d40683bfad711, fe2caefcdf5869f308c102e3d64d40683bfad711, fe2caefcdf5869f308c102e3d64d40683bfad711, fe2caefcdf5869f308c102e3d64d40683bfad711, fe2caefcdf5869f308c102e3d64d40683bfad711unaffected
LinuxLinux3.5, 0, 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, 6.18.30, 7.0.7, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.