Skip to main content
VulnerabilityPublished Updated

CVE-2026-23441: Linux kernel · net/mlx5e: Prevent concurrent access to IPSec ASO context

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in c3db55dc0f3344b62da25b025a8396d78763b5fa : update Linux kernel when convenient.

Data as of 5 Nov 2026, 22:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in c3db55dc0f3344b62da25b025a8396d78763b5fa, 6834d196107d5267dcad31b44211da7698e8f618, 99b36850d881e2d65912b2520a1c80d0fcc9429a +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1ed78fc033074c55221a80498204c539a3696877, < c3db55dc0f3344b62da25b025a8396d78763b5fa
Fixed in
  • c3db55dc0f3344b62da25b025a8396d78763b5fa
LinuxLinuxAffected
  • ≥ 1ed78fc033074c55221a80498204c539a3696877, < 6834d196107d5267dcad31b44211da7698e8f618
Fixed in
  • 6834d196107d5267dcad31b44211da7698e8f618
LinuxLinuxAffected
  • ≥ 1ed78fc033074c55221a80498204c539a3696877, < 99b36850d881e2d65912b2520a1c80d0fcc9429a
Fixed in
  • 99b36850d881e2d65912b2520a1c80d0fcc9429a
LinuxLinuxAffected
  • ≥ 1ed78fc033074c55221a80498204c539a3696877, < 99aaee927800ea00b441b607737f9f67b1899755
Fixed in
  • 99aaee927800ea00b441b607737f9f67b1899755
LinuxLinuxAffected
  • ≥ 1ed78fc033074c55221a80498204c539a3696877, < 2c6a5be0aee5a44066f68a332c30650900e32ad4
Fixed in
  • 2c6a5be0aee5a44066f68a332c30650900e32ad4
LinuxLinuxAffected
  • =6.2
Fixed in–

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.

References

Community reviews

Loading reviews…