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

net/mlx5e: Prevent concurrent access to IPSec ASO context

The query or updating IPSec offload object is through Access ASO WQE.
The driver uses a single mlx5e_ipsec_aso struct for each PF, which
contains a shared DMA-mapped context for all ASO operations.

A race condition exists because the ASO spinlock is released before
the hardware has finished processing WQE. If a second operation is
initiated immediately after, it overwrites the shared context in the
DMA area.

When the first operation's completion is processed later, it reads
this corrupted context, leading to unexpected behavior and incorrect
results.

This commit fixes the race by introducing a private context within
each IPSec offload object. The shared ASO context is now copied to
this private context while the ASO spinlock is held. Subsequent
processing uses this saved, per-object context, ensuring its integrity
is maintained.
Published: 2026-04-03
Score: 4.7 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Kernel data integrity and stability may be compromised via a race condition in the mlx5e IPSec offload driver.
Action: Apply patch
AI Analysis

Impact

A race condition exists in the Linux kernel’s mlx5e network driver, which manages IPSec offload (ASO) operations. The driver uses a single shared context for all ASO processes per physical function. Because the ASO spinlock is released before the hardware finishes processing the associated Work Queue Element, an immediate subsequent operation can overwrite the DMA‑mapped context. When the first operation finally completes, it reads this corrupted context, leading to incorrect results and unpredictable kernel behavior. The underlying weakness is a race condition between resource release and use (CWE‑821).

Affected Systems

The vulnerability affects Linux kernels that include the mlx5e driver with IPSec offload support. Any distribution or custom kernel that loads this driver prior to the applied fix is susceptible. Specific affected kernel versions are not enumerated in the available data, so all kernels using the unpatched mlx5e implementation should be considered at risk.

Risk and Exploitability

The CVSS score of 7.0 indicates a high severity, while the EPSS score of less than 1% suggests a low probability of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog, further indicating limited real‑world exploitation. Exploitation would likely require a race between remotely triggered IPSec offload transactions or privileged network traffic to trigger concurrent access, which is inferred from the description. If exploited, the attacker could cause kernel data corruption, potentially leading to privilege escalation or denial of service. The current impact is limited to improper driver behavior but could evolve into a broader system compromise if memory corruption occurs.

Generated by OpenCVE AI on April 7, 2026 at 09:49 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that contains the fix for the mlx5e IPSec offload race condition.
  • If an immediate kernel upgrade is not feasible, disable IPSec offload functionality in the mlx5e driver to prevent concurrent context access.
  • Monitor system logs for anomalous mlx5e driver behavior and verify that no IPSec offload processing occurs until the patch is applied.

Generated by OpenCVE AI on April 7, 2026 at 09:49 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 23 Apr 2026 21:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CPEs cpe:2.3:o:linux:linux_kernel:6.2:-:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 4.7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H'}


Tue, 07 Apr 2026 08:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CWE-665

Sat, 04 Apr 2026 01:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-821
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Moderate


Fri, 03 Apr 2026 21:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CWE-665

Fri, 03 Apr 2026 16:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Prevent concurrent access to IPSec ASO context The query or updating IPSec offload object is through Access ASO WQE. The driver uses a single mlx5e_ipsec_aso struct for each PF, which contains a shared DMA-mapped context for all ASO operations. A race condition exists because the ASO spinlock is released before the hardware has finished processing WQE. If a second operation is initiated immediately after, it overwrites the shared context in the DMA area. When the first operation's completion is processed later, it reads this corrupted context, leading to unexpected behavior and incorrect results. This commit fixes the race by introducing a private context within each IPSec offload object. The shared ASO context is now copied to this private context while the ASO spinlock is held. Subsequent processing uses this saved, per-object context, ensuring its integrity is maintained.
Title net/mlx5e: Prevent concurrent access to IPSec ASO context
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-04-13T06:07:31.326Z

Reserved: 2026-01-13T15:37:46.017Z

Link: CVE-2026-23441

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Analyzed

Published: 2026-04-03T16:16:26.340

Modified: 2026-04-23T20:59:07.087

Link: CVE-2026-23441

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-04-03T00:00:00Z

Links: CVE-2026-23441 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-04-08T19:53:58Z

Weaknesses