CVE-2026-68425: IB/mad: Drop unmatched RMPP responses before reassembly

Published Aug 10, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

IB/mad: Drop unmatched RMPP responses before reassembly

Kernel-handled RMPP receive processing starts reassembly for active DATA responses before the response is matched to an outstanding send. The normal match happens later, after ibprocessrmpprecvwc() has either assembled a complete message or consumed the segment.

That ordering lets an unsolicited response that routes to a kernel RMPP agent by the high TID bits allocate or extend RMPP receive state before the full TID and source address are checked against a real request. A reordered burst can therefore reach the receive-side insertion path even though the response would not match any send.

For kernel-handled RMPP DATA responses, require the existing ibfindsendmad() match before entering RMPP reassembly. The matcher already checks the full TID, management class and source address/GID against the agent wait, backlog and in-flight send lists. If there is no match, drop the response without creating RMPP state.

This leaves the RMPP window behavior unchanged and only rejects responses that have no corresponding request.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Update the Linux kernel so kernel-handled RMPP DATA receive processing matches incoming responses to outstanding sends (including full TID, management class, and source address/GID) before starting RMPP reassembly; if there is no corresponding request, drop the response without creating/extending RMPP receive state.

    Linux kernel (RMPP receive processing) RMPP receive reassembly state creation/matching order = Drop unmatched RMPP responses before reassembly

Event History

Aug 10, 2026
CVE Published
via MITRE·12:04 PM
Data Sourced
via MITRE·12:04 PM
Description
Data Sourced
via NVD·01:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68425?

CVE-2026-68425 has a risk rating of 37, indicating a moderate severity level.

2

How do I fix CVE-2026-68425?

To fix CVE-2026-68425, updating to the latest version of the Linux kernel where the vulnerability has been resolved is recommended.

3

What type of vulnerability is CVE-2026-68425?

CVE-2026-68425 is a vulnerability in the Linux kernel related to improper handling of RMPP responses.

4

What systems are affected by CVE-2026-68425?

CVE-2026-68425 affects systems running vulnerable versions of the Linux kernel.

5

What are the potential consequences of CVE-2026-68425?

The consequences of CVE-2026-68425 include potential denial of service due to improper processing of RMPP responses.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203