Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-46176: RDMA/mlx5: Fix error path fall-through in mlx5_ib_dev_res_srq_init()

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 6.6.140, 6fd93142dd1d09000c3750af08270f5792523fe9, a13c2ac4d480b734342c6fbf8249fc48afd675f3; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 6.6.140, 6fd93142dd1d09000c3750af08270f5792523fe9, a13c2ac4d480b734342c6fbf8249fc48afd675f3; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix error path fall-through in mlx5_ib_dev_res_srq_init() mlx5_ib_dev_res_srq_init() allocates two SRQs, s0 and s1. When ib_create_srq() fails for s1, the error branch destroys s0 but falls through and unconditionally assigns the freed s0 and the ERR_PTR s1 to devr->s0 and devr->s1. This leads to several problems: the lock-free fast path checks "if (devr->s1) return 0;" and treats the ERR_PTR as already initialised; users in mlx5_ib_create_qp() dereference the freed SRQ or ERR_PTR via to_msrq(devr->s0)->msrq.srqn; and mlx5_ib_dev_res_cleanup() dereferences the ERR_PTR and double-frees s0 on teardown. Fix by adding the same `goto unlock` in the s1 failure path.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 28, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-46176

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.6.64 and later · before 6.6.140
  • linux linux kernel6.11 and later · before 6.12.88
  • linux linux kernel6.13 and later · before 6.18.30
  • linux linux kernel6.19 and later · before 7.0.7
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.11affected
    • b6334d2356fc0922ed01457960f74923058a353a and later · before a13c2ac4d480b734342c6fbf8249fc48afd675f3affected · git
    • 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467 and later · before bc2cf5935b4665172235341163315905197ae91daffected · git
    • 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467 and later · before b087913ae88256df66620f7ba0a9776716aeef7eaffected · git
    • 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467 and later · before 6fd93142dd1d09000c3750af08270f5792523fe9affected · git
    • 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467 and later · before c488df06bd552bb8b6e14fa0cfd5ad986c6e9525affected · git
    • 6.6.64 and later · before 6.6.140affected · semver
    • before 6.11not affected · semver
    • 6.6.140 and later · up to and including 6.6.*not affected · semver
    • 6.12.88 and later · up to and including 6.12.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.29.1.el10_26.12.0-211.29.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-46174May 28, 2026 · x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache
    35Monitor
  • ← EarlierCVE-2026-46175May 28, 2026 · f2fs: fix fsck inconsistency caused by FGGC of node block
    28Monitor
  • Later →CVE-2026-46177May 28, 2026 · ipmi: Add limits to event and receive message requests
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux6.6.140Vendor (CNA)
Linux Linux6fd93142dd1d09000c3750af08270f5792523fe9Vendor (CNA)
Linux Linuxa13c2ac4d480b734342c6fbf8249fc48afd675f3Vendor (CNA)
Linux Linuxb087913ae88256df66620f7ba0a9776716aeef7eVendor (CNA)
Linux Linuxbc2cf5935b4665172235341163315905197ae91dVendor (CNA)
Linux Linuxc488df06bd552bb8b6e14fa0cfd5ad986c6e9525Vendor (CNA)
azl3 kernel 6.6.139.1-1 on Azure Linux 3.06.6.141.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-687.19.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.19.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.19.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.19.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.19.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.19.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.19.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.19.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.19.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.19.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.19.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.19.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.88-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.19.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.19.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.19.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.19.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.19.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.19.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.19.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.19.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.19.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-687.19.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+2

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-825 · Expired Pointer Dereference

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (11 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records