CVE-2026-23440 Details
Description
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix race condition during IPSec ESN update In IPSec full offload mode, the device reports an ESN (Extended Sequence Number) wrap event to the driver. The driver validates this event by querying the IPSec ASO and checking that the esn_event_arm field is 0x0, which indicates an event has occurred. After handling the event, the driver must re-arm the context by setting esn_event_arm back to 0x1. A race condition exists in this handling path. After validating the event, the driver calls mlx5_accel_esp_modify_xfrm() to update the kernel's xfrm state. This function temporarily releases and re-acquires the xfrm state lock. So, need to acknowledge the event first by setting esn_event_arm to 0x1. This prevents the driver from reprocessing the same ESN update if the hardware sends events for other reason. Since the next ESN update only occurs after nearly 2^31 packets are received, there's no risk of missing an update, as it will happen long after this handling has finished. Processing the event twice causes the ESN high-order bits (esn_msb) to be incremented incorrectly. The driver then programs the hardware with this invalid ESN state, which leads to anti-replay failures and a complete halt of IPSec traffic. Fix this by re-arming the ESN event immediately after it is validated, before calling mlx5_accel_esp_modify_xfrm(). This ensures that any spurious, duplicate events are correctly ignored, closing the race window.
A race condition vulnerability has been identified in the Linux kernel's handling of Extended Sequence Number (ESN) updates in IPSec full offload mode. When the device reports an ESN wrap event, the driver must validate this event and then re-arm the context to prevent reprocessing the same update. However, the current handling introduces a race condition, allowing the event to be processed twice. This mismanagement causes the ESN high-order bits to be incorrectly incremented, leading the driver to program the hardware with an invalid ESN state. The consequence is anti-replay failures and a complete halt of IPSec traffic.
The vulnerability has been addressed by modifying the driver to re-arm the ESN event immediately after validation, before updating the xfrm state. Users should apply the latest patches available in the Linux kernel stable tree to mitigate this issue.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2051c709dce92da3550040aa7949cd5a9c89b14e | kernel.org | Patch |
| https://git.kernel.org/stable/c/3dffc083292e6872787bd7e34b957627622f9af4 | kernel.org | Patch |
| https://git.kernel.org/stable/c/8d625c15471fb8780125eaef682983a96af77bdc | kernel.org | Patch |
| https://git.kernel.org/stable/c/96c9c25b74686ac2de15921c9ad30c5ef13af8cd | kernel.org | Patch |
| https://git.kernel.org/stable/c/beb6e2e5976a128b0cccf10d158124422210c5ef | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.4.1, < 6.6.130 >= 6.7, < 6.12.78 >= 6.13, < 6.18.20 >= 6.19, < 6.19.10 6.4 - 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 7.0 rc5 7.0 rc6 7.0 rc7 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 24, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Apr 27, 2026 | CVE Modified | kernel.org |
| Apr 23, 2026 | Initial Analysis | [email protected] |
| Apr 3, 2026 | New CVE Received | kernel.org |