Linux Kernel up to 7.1-rc2 RDMA mlx4_ib_create_srq memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.6$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Linux Kernel up to 6.6.139/6.12.87/6.18.29/7.0.6/7.1-rc2. Affected by this vulnerability is the function mlx4_ib_create_srq of the component RDMA. The manipulation leads to memory leak. This vulnerability is documented as CVE-2026-46178. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.139/6.12.87/6.18.29/7.0.6/7.1-rc2. It has been rated as critical. This issue affects the function mlx4_ib_create_srq of the component RDMA. The manipulation with an unknown input leads to a memory leak vulnerability. Using CWE to declare the problem leads to CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. Impacted is availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() Sashiko points out that mlx4_srq_alloc() was not undone during error unwind, add the missing call to mlx4_srq_free().

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-46178 since 05/13/2026. Technical details are known, but no exploit is available.

Upgrading to version 6.6.140, 6.12.88, 6.18.30, 7.0.7 or 7.1-rc3 eliminates this vulnerability. Applying the patch c5dc30da990045105c9762248d23076223e7878a/0dbd619716fb07b7de1acd64fec673ee6e1adde7/e01b8c9286c470b71a38acd320106f2c4f2826a1/388617f44d81604a760742a0b5de292d411e63e3/c54c7e4cb679c0aaa1cb489b9c3f2cd98e63a44c is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-32805). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.7
VulDB Meta Temp Score: 6.6

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 7.8
CNA Vector (Linux): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.140/6.12.88/6.18.30/7.0.7/7.1-rc3
Patch: c5dc30da990045105c9762248d23076223e7878a/0dbd619716fb07b7de1acd64fec673ee6e1adde7/e01b8c9286c470b71a38acd320106f2c4f2826a1/388617f44d81604a760742a0b5de292d411e63e3/c54c7e4cb679c0aaa1cb489b9c3f2cd98e63a44c

Timelineinfo

05/13/2026 CVE reserved
05/28/2026 +15 days Advisory disclosed
05/28/2026 +0 days VulDB entry created
06/11/2026 +14 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-46178 (🔒)
GCVE (CVE): GCVE-0-2026-46178
GCVE (VulDB): GCVE-100-366641
EUVD: 🔒

Entryinfo

Created: 05/28/2026 13:26
Updated: 06/11/2026 06:30
Changes: 05/28/2026 13:26 (59), 05/31/2026 12:10 (1), 06/11/2026 06:30 (11)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!