[CVE-2026-64522][LOW] net/mlx5e: Fix eswitch mode block underflow on IPsec acquire SA [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-64522
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: net/mlx5e: Fix eswitch mode block underflow on IPsec acquire SA [ Upstream
Commit: b5bd4249e430f5963d559708ee96a671716d2400
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b5bd4249e430f5963d559708ee96a671716d2400
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64522
Analysis date: Sat, 25 Jul 2026 15:05:18 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
An acquire-flow IPsec SA in mlx5e could incorrectly unblock eswitch mode without a matching block operation, causing a mode block counter underflow and possible local driver availability impact, but exploitation normally requires administrative XFRM offload control and no memory corruption primitive is shown.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-64522 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64522

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-64522	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-191;CWE-682;CWE-703;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'mlx5e_xfrm_add_state mishandles acquire flow temporary IPsec SAs. The acquire path allocates software state and skips hardware offload setup, but it previously jumped to a common success path that can call mlx5_eswitch_unblock_mode without a matching mlx5_eswitch_block_mode, causing an eswitch mode block counter underflow. This is a local control plane issue in mlx5 IPsec offload handling and is not reachable by network packet traffic alone. For the CVSS the PR:L is used for the paranoid score because a delegated network administration process or reduced capability root with XFRM offload control could trigger the path, although typical systems require administrative control. Impact is mainly denial of service or incorrect driver mode blocking for the mlx5 eswitch. No concrete memory corruption, information leak, or privilege escalation primitive is visible from the code path.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)  SKIP CVE-2026-64522 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE OOB DANGER SIMPLEFIX NETWORK HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=2
ActionableScoreLower=1

## 1. ActionableScore

* Conservative score: 1
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

Conservative signals:

* Availability impact realistic: +1. The counter underflow can leave mlx5 eswitch mode blocking state inconsistent and may cause driver or device-management disruption.
* Requires admin/root/CAP_NET_ADMIN in typical deployments: -2. Creating or controlling XFRM/IPsec offload state normally requires administrative network privileges.
* No memory corruption signal: +0. The patch shows an unmatched decrement of a mode-blocking counter, not UAF, OOB write, double free, object reuse, or attacker-controlled overwrite.
* No remote/network-triggerable signal: +0. The affected path is XFRM/IPsec offload control-plane setup, not packet receive processing.

Paranoid additional signal:

* Privileged device-management state corruption concern: +1. The underflow affects trusted mlx5 eswitch offload bookkeeping and may persistently distort mode-blocking behavior until recovery or reload.

## 3. Reachability analysis

The bug is reachable through mlx5e XFRM/IPsec offload state creation, specifically the acquire-flow temporary SA path with `XFRM_DEV_OFFLOAD_FLAG_ACQ`. In normal deployments this requires root or CAP_NET_ADMIN and suitable mlx5 hardware with IPsec offload support. It is not triggered by ordinary inbound network packets alone. Namespaces or containers can matter only if a reduced-privilege or delegated network-administration context is allowed to manage the relevant XFRM offload state, which supports the paranoid PR:L-style interpretation but not a fully unprivileged trigger.

Call-site confidence: high. The provided diff and commit message describe the exact control-flow mismatch between `mlx5_eswitch_block_mode()` and `mlx5_eswitch_unblock_mode()`.

## 4. Severity interpretation

This behaves more like an ordinary Moderate or Low-like driver state bug than an Important-class vulnerability. The realistic impact is device or driver availability degradation caused by an eswitch mode block counter underflow. There is no evidence of a practical privilege escalation path, confidentiality impact, integrity impact, UAF, reclaim primitive, arbitrary write, or type confusion. The paranoid score keeps some manual-triage awareness for persistent trusted device-state corruption, but it remains below Actionable Moderate.

## 5. One-sentence report phrase

An acquire-flow IPsec SA in mlx5e could incorrectly unblock eswitch mode without a matching block operation, causing a mode block counter underflow and possible local driver availability impact, but exploitation normally requires administrative XFRM offload control and no memory corruption primitive is shown.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

The issue is a local privileged mlx5/IPsec offload bookkeeping underflow with no demonstrated memory corruption, privilege escalation, information disclosure, or network packet trigger.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: net/mlx5e: Fix eswitch mode block underflow on IPsec acquire SA [ Upstream
Commit: b5bd4249e430f5963d559708ee96a671716d2400
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b5bd4249e430f5963d559708ee96a671716d2400

Changed files:
  drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b5bd4249e430f5963d559708ee96a671716d2400

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-64522 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64522

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.5

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 1
  Paranoid ActionableScore: 2

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).