CyberSecBulletin
CVE-2026-72065NVD status: Received

In the Linux kernel, the following vulnerability has been resolved: net: mana: Validate the…

Published Updated By the CyberSecBulletin desk

CVE-2026-72065 is a critical-severity improper input validation vulnerability in Linux, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions a631f82f89c76084ad5b2b9c043d3b391ffa56d8, d2568e64d01f480200063fadd67d6938f676c66f, 2e276b14b6d378372bf0152df89286cbe7632fb0 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.73% chance of exploitation within 30 days, higher than 55% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Linux to a631f82f89c76084ad5b2b9c043d3b391ffa56d8 or d2568e64d01f480200063fadd67d6938f676c66f or 2e276b14b6d378372bf0152df89286cbe7632fb0 or 6080189291d958604dcefe513a13900835ac982f, whichever matches your release line, or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxca9c54d2d6a5ab2430c4eda364c77125d62e5e0f up to, but not including, a631f82f89c76084ad5b2b9c043d3b391ffa56d8; ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f up to, but not including, d2568e64d01f480200063fadd67d6938f676c66f; ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f up to, but not including, 2e276b14b6d378372bf0152df89286cbe7632fb0; ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f up to, but not including, 6080189291d958604dcefe513a13900835ac982f; ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f up to, but not including, 6d13eaa13341a8f80aaf86f78591e1b1d393711d; ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f up to, but not including, 282c5214ca4eb3799158c76782646e86d2945d1b; ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f up to, but not including, 2e2a83b4998af4384e677d3b2ac08565274279bf; 5.13a631f82f89c76084ad5b2b9c043d3b391ffa56d8, d2568e64d01f480200063fadd67d6938f676c66f, 2e276b14b6d378372bf0152df89286cbe7632fb0, 6080189291d958604dcefe513a13900835ac982f, 6d13eaa13341a8f80aaf86f78591e1b1d393711d, 282c5214ca4eb3799158c76782646e86d2945d1b

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
NetworkCan be exploited remotely over a network, including the internet.
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
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

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

Official description

In the Linux kernel, the following vulnerability has been resolved: net: mana: Validate the packet length reported by the NIC Validate the packet length reported in the RX CQE before passing it to skb processing. The CQE is supplied by the NIC device and should not be blindly trusted.

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

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

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

References

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.