CVE-2026-23440: net/mlx5e: Fix race condition during IPSec ESN update
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 2051c709dce92da3550040aa7949cd5a9c89b14e, 3dffc083292e6872787bd7e34b957627622f9af4, 8d625c15471fb8780125eaef682983a96af77bdc.
- Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 4.7.
Low priority for now. Upgrade to Linux Linux 2051c709dce92da3550040aa7949cd5a9c89b14e, 3dffc083292e6872787bd7e34b957627622f9af4, 8d625c15471fb8780125eaef682983a96af77bdc or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 3, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-362
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.7
- CNA · Linux
- 7.5
- 2.8 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.4.1 and later · before 6.6.130
- linux linux kernel6.7 and later · before 6.12.78
- linux linux kernel6.13 and later · before 6.18.20
- linux linux kernel6.19 and later · before 6.19.10
- linux linux kernel6.4
- linux linux kernel7.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.4affected
- fef06678931ff67b158d337b581e5cf5ca40a3a3 and later · before 3dffc083292e6872787bd7e34b957627622f9af4affected · git
- fef06678931ff67b158d337b581e5cf5ca40a3a3 and later · before 2051c709dce92da3550040aa7949cd5a9c89b14eaffected · git
- fef06678931ff67b158d337b581e5cf5ca40a3a3 and later · before 96c9c25b74686ac2de15921c9ad30c5ef13af8cdaffected · git
- fef06678931ff67b158d337b581e5cf5ca40a3a3 and later · before 8d625c15471fb8780125eaef682983a96af77bdcaffected · git
- fef06678931ff67b158d337b581e5cf5ca40a3a3 and later · before beb6e2e5976a128b0cccf10d158124422210c5efaffected · git
- before 6.4not affected · semver
- 6.6.130 and later · up to and including 6.6.*not affected · semver
- 6.12.78 and later · up to and including 6.12.*not affected · semver
- 6.18.20 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.10-1 | 6.19.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-23438Apr 3, 2026 · net: mvpp2: guard flow control update with global_tx_fc in buffer switching22Monitor
- ← EarlierCVE-2026-23439Apr 3, 2026 · udp_tunnel: fix NULL deref caused by udp_sock_create6 when CONFIG_IPV6=n22Monitor
- Later →CVE-2026-23441Apr 3, 2026 · net/mlx5e: Prevent concurrent access to IPSec ASO context18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2051c709dce92da3550040aa7949cd5a9c89b14e | Vendor (CNA) |
| Linux Linux | 3dffc083292e6872787bd7e34b957627622f9af4 | Vendor (CNA) |
| Linux Linux | 8d625c15471fb8780125eaef682983a96af77bdc | Vendor (CNA) |
| Linux Linux | 96c9c25b74686ac2de15921c9ad30c5ef13af8cd | Vendor (CNA) |
| Linux Linux | beb6e2e5976a128b0cccf10d158124422210c5ef | Vendor (CNA) |
| debian:linux | 6.12.85-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.