CVE-2026-43199

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

net/mlx5e: Fix "scheduling while atomic" in IPsec MAC address query - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e1407fb7c337373dfaaae2445d828b0b9ae26a29
generic

net/mlx5e: Fix "scheduling while atomic" in IPsec MAC address query - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/859380694f434597407632c29f30fdb5e763e6cc
generic

net/mlx5e: Fix "scheduling while atomic" in IPsec MAC address query - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57957bc7f1865778ec9b1618e15515feb6df7eb4
generic

net/mlx5e: Fix "scheduling while atomic" in IPsec MAC address query - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/546de94e41e92e1f7dc6213615fb7c794d05db98

Vendor Advisories for CVE-2026-43199(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (113 versions)6.19.6-1

All Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 5× in last 7d / 68× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 200 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-23 20:02 UTCEG score recompute
  11. 2026-08-23 20:02 UTCVendor advisory
  12. 2026-08-23 20:01 UTCGHSA enrichment
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 12:56 UTCEG score recompute
  20. 2026-08-17 12:56 UTCVendor advisory
  21. 2026-08-17 12:56 UTCGHSA enrichment
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 04:53 UTCEG score recompute
  24. 2026-08-16 04:53 UTCVendor advisory
  25. 2026-08-16 04:53 UTCGHSA enrichment
Show 75 more
  1. 2026-08-16 02:14 UTCEPSS rescore
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 15:55 UTCVendor advisory
  4. 2026-08-14 15:55 UTCGHSA enrichment
  5. 2026-08-14 03:28 UTCEG score recompute
  6. 2026-08-14 03:28 UTCVendor advisory
  7. 2026-08-14 03:28 UTCGHSA enrichment
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 06:07 UTCVendor advisory
  10. 2026-08-13 06:07 UTCGHSA enrichment
  11. 2026-08-12 17:01 UTCEG score recompute
  12. 2026-08-12 17:01 UTCVendor advisory
  13. 2026-08-12 17:00 UTCGHSA enrichment
  14. 2026-08-12 13:51 UTCEPSS rescore
  15. 2026-08-11 16:00 UTCEG score recompute
  16. 2026-08-11 16:00 UTCVendor advisory
  17. 2026-08-11 16:00 UTCGHSA enrichment
  18. 2026-08-11 13:43 UTCEPSS rescore
  19. 2026-08-11 01:32 UTCEG score recompute
  20. 2026-08-11 01:32 UTCVendor advisory
  21. 2026-08-11 01:32 UTCGHSA enrichment
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 03:29 UTCVendor advisory
  24. 2026-08-10 03:29 UTCGHSA enrichment
  25. 2026-08-09 15:02 UTCEG score recompute
  26. 2026-08-09 15:02 UTCVendor advisory
  27. 2026-08-09 15:02 UTCGHSA enrichment
  28. 2026-08-09 13:46 UTCEPSS rescore
  29. 2026-08-09 02:35 UTCEG score recompute
  30. 2026-08-09 02:35 UTCVendor advisory
  31. 2026-08-09 02:35 UTCGHSA enrichment
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 12:08 UTCVendor advisory
  34. 2026-08-08 12:08 UTCGHSA enrichment
  35. 2026-08-07 23:41 UTCEG score recompute
  36. 2026-08-07 23:41 UTCVendor advisory
  37. 2026-08-07 23:41 UTCGHSA enrichment
  38. 2026-08-07 11:14 UTCVendor advisory
  39. 2026-08-07 11:14 UTCGHSA enrichment
  40. 2026-08-06 16:54 UTCEG score recompute
  41. 2026-08-06 16:54 UTCVendor advisory
  42. 2026-08-06 16:54 UTCGHSA enrichment
  43. 2026-08-06 13:46 UTCEPSS rescore
  44. 2026-08-06 02:18 UTCEG score recompute
  45. 2026-08-06 02:18 UTCVendor advisory
  46. 2026-08-06 02:18 UTCGHSA enrichment
  47. 2026-08-05 19:17 UTCEPSS rescore
  48. 2026-08-05 13:51 UTCEG score recompute
  49. 2026-08-05 13:51 UTCVendor advisory
  50. 2026-08-05 13:51 UTCGHSA enrichment
  51. 2026-08-04 15:10 UTCEPSS rescore
  52. 2026-08-04 10:38 UTCEPSS rescore
  53. 2026-08-03 19:52 UTCEG score recompute
  54. 2026-08-03 19:52 UTCVendor advisory
  55. 2026-08-03 19:52 UTCGHSA enrichment
  56. 2026-08-03 10:36 UTCEPSS rescore
  57. 2026-08-02 17:35 UTCVendor advisory
  58. 2026-08-02 17:35 UTCGHSA enrichment
  59. 2026-08-02 05:08 UTCEG score recompute
  60. 2026-08-02 05:08 UTCVendor advisory
  61. 2026-08-02 05:08 UTCGHSA enrichment
  62. 2026-08-02 02:27 UTCEPSS rescore
  63. 2026-08-01 04:16 UTCEPSS rescore
  64. 2026-07-30 16:28 UTCEPSS rescore
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-28 15:36 UTCEPSS rescore
  67. 2026-07-27 14:13 UTCEPSS rescore
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-26 14:54 UTCEPSS rescore
  70. 2026-07-25 14:18 UTCEPSS rescore
  71. 2026-07-24 14:17 UTCEPSS rescore
  72. 2026-07-23 14:18 UTCEPSS rescore
  73. 2026-07-23 03:13 UTCEG score recompute
  74. 2026-07-22 14:08 UTCEPSS rescore
  75. 2026-07-21 15:24 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43199?
CVE-2026-43199 is a high vulnerability published on May 6, 2026. 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 mlx5eipsecinit_macs() by replacing mlx5querymacaddress() with etheraddr_copy() to get the local MAC address directly from…
When was CVE-2026-43199 disclosed?
CVE-2026-43199 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43199 actively exploited?
CVE-2026-43199 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.1% of all scored CVEs.
What is the CVSS score of CVE-2026-43199?
CVE-2026-43199 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-43199?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43199, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43199

Explore →

Is Your Infrastructure Affected by CVE-2026-43199?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.