Vulnerability · Published May 6, 2026 · Assigned by Linux
CVE-2026-43199net/mlx5e: Fix "scheduling while atomic" in IPsec MAC address query
High 7.5
In plain English
A high-severity race condition in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 36% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:13 | linux | 6.12.85-1 | DEBIAN-CVE-2026-43199 |
| Debian:14 | linux | 6.19.6-1 | DEBIAN-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux | 6.8.0-134.134 | UBUNTU-CVE-2026-43199 |
| Ubuntu:25.10 | linux | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1060.63 | UBUNTU-CVE-2026-43199 |
| Ubuntu:25.10 | linux-aws | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1060.63~22.04.1 | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1063.71 | UBUNTU-CVE-2026-43199 |
| Ubuntu:25.10 | linux-azure | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1063.71~22.04.1 | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1062.69 | UBUNTU-CVE-2026-43199 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1062.69~22.04.1 | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1063.69 | UBUNTU-CVE-2026-43199 |
| Ubuntu:25.10 | linux-gcp | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1063.69~22.04.1 | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1058.64 | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1045.48 | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-136.136~22.04.1 | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1060.61 | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1060.61~22.04.1 | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-134.134.1 | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-134.134.1~22.04.1 | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1058.61 | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1058.61~22.04.1 | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1058.61.1 | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1029.30 | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1057.58 | UBUNTU-CVE-2026-43199 |
| Ubuntu:25.10 | linux-oracle | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1057.58~22.04.1 | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1060.64 | UBUNTU-CVE-2026-43199 |
| Ubuntu:25.10 | linux-raspi | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:25.10 | linux-realtime | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:25.10 | linux-riscv | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-134.134~22.04.1 | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-43199 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1032.33 | UBUNTU-CVE-2026-43199 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | cee137a634318bfbda18ee5af45d300153b57fa5 – before 5efde07521309274f26727860774614cbc187242cee137a634318bfbda18ee5af45d300153b57fa5 – before e1407fb7c337373dfaaae2445d828b0b9ae26a29cee137a634318bfbda18ee5af45d300153b57fa5 – before 57957bc7f1865778ec9b1618e15515feb6df7eb4cee137a634318bfbda18ee5af45d300153b57fa5 – before 546de94e41e92e1f7dc6213615fb7c794d05db98cee137a634318bfbda18ee5af45d300153b57fa5 – before 859380694f434597407632c29f30fdb5e763e6cc |
| Linux | Linux | 6.2 |
Weakness: CWE-362 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References
- https://git.kernel.org/stable/c/5efde07521309274f26727860774614cbc187242
- https://git.kernel.org/stable/c/e1407fb7c337373dfaaae2445d828b0b9ae26a29
- https://git.kernel.org/stable/c/57957bc7f1865778ec9b1618e15515feb6df7eb4
- https://git.kernel.org/stable/c/546de94e41e92e1f7dc6213615fb7c794d05db98
- https://git.kernel.org/stable/c/859380694f434597407632c29f30fdb5e763e6cc