CyberSecBulletin
CVE-2026-68425NVD status: Received

Linux: Uncontrolled Resource Consumption

Published Updated By the CyberSecBulletin desk

CVE-2026-68425 is a high-severity uncontrolled resource consumption vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions 45416c87ebcece1e90f3bc5bc172d106b77c6b69, 9634fb1f4d404f36a20ffbcb8797369db69b06bb, bfb9e8243fd2099d1080d09222964d988f991d9b as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.26% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 45416c87ebcece1e90f3bc5bc172d106b77c6b69 or 9634fb1f4d404f36a20ffbcb8797369db69b06bb or bfb9e8243fd2099d1080d09222964d988f991d9b or dfa535c94406c03d3f0c869ef3ba5528e395737c, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxfa619a77046bef30478697aba0553991033afb8e up to, but not including, 45416c87ebcece1e90f3bc5bc172d106b77c6b69; fa619a77046bef30478697aba0553991033afb8e up to, but not including, 9634fb1f4d404f36a20ffbcb8797369db69b06bb; fa619a77046bef30478697aba0553991033afb8e up to, but not including, bfb9e8243fd2099d1080d09222964d988f991d9b; fa619a77046bef30478697aba0553991033afb8e up to, but not including, dfa535c94406c03d3f0c869ef3ba5528e395737c; fa619a77046bef30478697aba0553991033afb8e up to, but not including, 6e1bd7f590b0ccfee07f7fe1d48b92059bd37d72; fa619a77046bef30478697aba0553991033afb8e up to, but not including, 98d2d468b4faa1fdc68c0c6c238389906ee3490c; fa619a77046bef30478697aba0553991033afb8e up to, but not including, ad9c9ad3204f63a46f0f7de29687a8e512f05e29; fa619a77046bef30478697aba0553991033afb8e up to, but not including, d2e52d610b9b09694261632340b801a421e0b0c5; and 1 more ranges45416c87ebcece1e90f3bc5bc172d106b77c6b69, 9634fb1f4d404f36a20ffbcb8797369db69b06bb, bfb9e8243fd2099d1080d09222964d988f991d9b, dfa535c94406c03d3f0c869ef3ba5528e395737c, 6e1bd7f590b0ccfee07f7fe1d48b92059bd37d72, 98d2d468b4faa1fdc68c0c6c238389906ee3490c

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
LowLimited modification of data is possible.
Availability
HighThe component can be taken down completely.

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

Official description

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 ib_process_rmpp_recv_wc() 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 ib_find_send_mad() 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How developers prevent this class of flaw

  • Ensure that protocols have specific limits of scale placed on them.
  • Ensure that all failures in resource allocation place the system into a safe posture.

More Uncontrolled Resource Consumption vulnerabilities (CWE-400)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Uncontrolled Resource Consumption vulnerabilities

Spotted an error? Tell us.