CVE-2026-43199: net/mlx5e: Fix "scheduling while atomic" in IPsec MAC address query
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: Fix "scheduling while atomic" in IPsec MAC address query
Fix a "scheduling while atomic" bug in mlx5e_ipsec_init_macs() by
replacing mlx5_query_mac_address() with ether_addr_copy() to get the
local MAC address directly from netdev->dev_addr.
The issue occurs because mlx5_query_mac_address() queries the hardware
which involves mlx5_cmd_exec() that can sleep, but it is called from
the mlx5e_ipsec_handle_event workqueue which runs in atomic context.
The MAC address is already available in netdev->dev_addr, so no need
to query hardware. This avoids the sleeping call and resolves the bug.
Call trace:
BUG: scheduling while atomic: kworker/u112:2/69344/0x00000200
__schedule+0x7ab/0xa20
schedule+0x1c/0xb0
schedule_timeout+0x6e/0xf0
__wait_for_common+0x91/0x1b0
cmd_exec+0xa85/0xff0 [mlx5_core]
mlx5_cmd_exec+0x1f/0x50 [mlx5_core]
mlx5_query_nic_vport_mac_address+0x7b/0xd0 [mlx5_core]
mlx5_query_mac_address+0x19/0x30 [mlx5_core]
mlx5e_ipsec_init_macs+0xc1/0x720 [mlx5_core]
mlx5e_ipsec_build_accel_xfrm_attrs+0x422/0x670 [mlx5_core]
mlx5e_ipsec_handle_event+0x2b9/0x460 [mlx5_core]
process_one_work+0x178/0x2e0
worker_thread+0x2ea/0x430
Security readout for executives and security teams
Plain-English summary
A Linux mlx5 Ethernet/IPsec driver path can attempt a sleep-capable hardware query while running in an atomic context. This can trigger a kernel scheduling fault and disrupt availability. Exposure appears limited to systems using the affected mlx5e IPsec functionality, rather than all Linux installations.
Executive priority
Treat as a high-priority availability issue for network, virtualization, or appliance infrastructure using mlx5e IPsec acceleration. Promptly establish exposure and patch affected systems through supported kernel channels. Systems without the relevant driver and IPsec path are lower priority, subject to vendor confirmation.
Technical view
mlx5e_ipsec_init_macs() calls mlx5_query_mac_address(), which reaches mlx5_cmd_exec() and may sleep. The call originates from mlx5e_ipsec_handle_event in atomic context, producing a “scheduling while atomic” fault. The stable fix copies the already available MAC address from netdev->dev_addr with ether_addr_copy(), avoiding the hardware query.
Likely exposure
Most likely exposed are affected Linux kernels on hosts using the mlx5e driver and its IPsec acceleration event path. The supplied version data lists 6.2, 6.12.75, 6.18.16, 6.19.6, and 7.0, but its exact range semantics are unclear; confirm applicability through distribution or kernel-vendor guidance.
Exploitation context
The supplied record scores availability impact as high with CVSS 3.1 score 7.5 and a network vector. However, it provides no demonstrated attack scenario, exploit publication, or evidence of active exploitation, and the CVE is not listed as KEV in the bundle.
Researcher notes
The root cause and corrective code change are clearly described, but the bundle does not establish practical remote triggerability or the precise affected-version intervals. The CVSS network vector should not be interpreted as proven unauthenticated exploitation. Validate configuration reachability, vendor backports, and commit ancestry before declaring a host vulnerable.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fix.
Ask the Linux distribution or appliance vendor to confirm affected and corrected package versions.
Prioritize mlx5e hosts using IPsec acceleration when scheduling updates.
Apply normal kernel-update rollback and availability planning for production systems.
Validation and detection
Inventory kernel versions on systems using mlx5 hardware or the mlx5e driver.
Determine whether mlx5e IPsec acceleration is enabled or operationally used.
Confirm the installed kernel contains the applicable referenced stable commit or vendor backport.
Review kernel logs for “scheduling while atomic” traces involving mlx5e_ipsec_init_macs or mlx5_cmd_exec.
Retest relevant IPsec operations after updating and monitor for recurrence.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43199 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.