net/mlx5e: Prevent concurrent access to IPSec ASO context
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s net/mlx5e driver uses a shared DMA-mapped context for IPSec offload operations. Concurrent operations can overwrite that context before hardware processing finishes, causing unexpected behavior and incorrect results. The input does not specify an attacker route, authentication requirement, or user interaction.
Engineers running Linux kernels with the net/mlx5e IPSec offload driver should check their kernel vendor’s advisory; affected versions are not specified.