LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46112: RDMA/hns: Fix unlocked call to hns_roce_qp_remove()

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

An error path in Linux’s HNS RoCE RDMA driver can remove a queue pair without required locks, risking kernel memory corruption. The severity model assumes a local, low-privileged attacker and potential confidentiality, integrity, and availability impact. Practical exploitation is not established. Risk is concentrated on affected kernels using this driver.

Executive priority

Prioritize remediation on multi-user, compute, or infrastructure systems actively using HNS RoCE/RDMA. The potential kernel-memory impact is serious, but the local-access requirement and absence of documented exploitation reduce emergency internet-edge urgency. Handle through an expedited kernel maintenance cycle after confirming exposure.

Technical view

In hns_roce_create_qp_common(), error unwinding calls hns_roce_qp_remove() without locks required by that function. Concurrent state changes may corrupt kernel memory. The fix acquires the same locks used by other callers. CVSS 3.1 is 7.8: local access, low complexity, low privileges, and no user interaction. Exact triggering conditions are not supplied.

Likely exposure

Likely exposure is limited to affected Linux kernels where HNS RoCE/RDMA is present and the vulnerable queue-pair creation error path is reachable. The supplied version data spans Linux 4.17 through 7.1 but includes an unexplained “0” and ambiguous entries. Confirm distribution-specific exposure and backports rather than relying solely on version strings.

Exploitation context

The bundle marks KEV false and contains no cited evidence of active exploitation or a public proof of concept. The CVSS vector indicates local rather than network access. Whether the error path can be triggered reliably and whether memory corruption can be converted into controlled security impact are not established by the supplied evidence.

Researcher notes

The defect is an unlocked hns_roce_qp_remove() call during hns_roce_create_qp_common() error unwinding. The correction mirrors locking used by two other callers. No CWE is assigned. The source bundle does not describe the race window, trigger prerequisites, observed crashes, exploit reliability, or distribution backport status, limiting deeper exploitability assessment.

Mitigation direction

  • Inventory affected Linux systems where HNS RoCE/RDMA is configured or active.
  • Install a vendor-supported kernel containing the applicable referenced stable fix for that branch.
  • If patching is delayed, consult the distribution vendor; the sources name no tested interim mitigation.
  • Reduce untrusted local access on exposed systems until remediation is complete.

Validation and detection

  • Record running kernel versions and map vendor builds to upstream fix commits or documented backports.
  • Confirm whether the hns_roce driver and relevant RDMA hardware are present, configured, or active.
  • After updating, verify the remediated kernel is booted and the vulnerable code is patched.
  • Run approved RDMA regression tests covering queue-pair creation and error handling.
Prepared
Confidence
medium
Sources
9

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-46112 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
0ADP providers
8Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-46112Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe088a685eae94a0607b8f7b99949a0e14d748813, e088a685eae94a0607b8f7b99949a0e14d748813, e088a685eae94a0607b8f7b99949a0e14d748813, e088a685eae94a0607b8f7b99949a0e14d748813, e088a685eae94a0607b8f7b99949a0e14d748813, e088a685eae94a0607b8f7b99949a0e14d748813, e088a685eae94a0607b8f7b99949a0e14d748813unaffected
LinuxLinux4.17, 0, 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.