CVE-2026-23000

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-01-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net/mlx5e: Fix crash on profile change rollback failure

mlx5e_netdev_change_profile can fail to attach a new profile and can fail to rollback to old profile, in such case, we could end up with a dangling netdev with a fully reset netdev_priv. A retry to change profile, e.g. another attempt to call mlx5e_netdev_change_profile via switchdev mode change, will crash trying to access the now NULL priv->mdev.

This fix allows mlx5e_netdev_change_profile() to handle previous failures and an empty priv, by not assuming priv is valid.

Pass netdev and mdev to all flows requiring mlx5e_netdev_change_profile() and avoid passing priv. In mlx5e_netdev_change_profile() check if current priv is valid, and if not, just attach the new profile without trying to access the old one.

This fixes the following oops, when enabling switchdev mode for the 2nd time after first time failure:

## Enabling switchdev mode first time:

mlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload workqueue: Failed to create a rescuer kthread for wq "mlx5e": -EINTR mlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12 mlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12 workqueue: Failed to create a rescuer kthread for wq "mlx5e": -EINTR mlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12 mlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12 ^^^^^^^^ mlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)

## retry: Enabling switchdev mode 2nd time:

mlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload BUG: kernel NULL pointer dereference, address: 0000000000000038 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 RIP: 0010:mlx5e_detach_netdev+0x3c/0x90 Code: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 <48> 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07 RSP: 0018:ffffc90000673890 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000 RDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000 RBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000 R10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000 R13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000 FS: 00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0 Call Trace: mlx5e_netdev_change_profile+0x45/0xb0 mlx5e_vport_rep_load+0x27b/0x2d0 mlx5_esw_offloads_rep_load+0x72/0xf0 esw_offloads_enable+0x5d0/0x970 mlx5_eswitch_enable_locked+0x349/0x430 ? is_mp_supported+0x57/0xb0 mlx5_devlink_eswitch_mode_set+0x26b/0x430 devlink_nl_eswitch_set_doit+0x6f/0xf0 genl_family_rcv_msg_doit+0xe8/0x140 genl_rcv_msg+0x18b/0x290 ? __pfx_devlink_nl_pre_doit+0x10/0x10 ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10 ? __pfx_devlink_nl_post_doit+0x10/0x10 ? __pfx_genl_rcv_msg+0x10/0x10 netlink_rcv_skb+0x52/0x100 genl_rcv+0x28/0x40 netlink_unicast+0x282/0x3e0 ? __alloc_skb+0xd6/0x190 netlink_sendmsg+0x1f7/0x430 __sys_sendto+0x213/0x220 ? __sys_recvmsg+0x6a/0xd0 __x64_sys_sendto+0x24/0x30 do_syscall_64+0x50/0x1f0 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7fdfb8495047

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

January 25, 2026

Last Modified

June 17, 2026

References (3)

Vendor Advisories for CVE-2026-23000(1)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-06-08ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-06-08ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-06-08ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-06-08ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-06-08ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-06-08ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-06-08ubuntu
linuxKernel @ 6.12.67—osv

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(7)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 43× 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 109 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-23000?
CVE-2026-23000 is a medium vulnerability published on January 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix crash on profile change rollback failure mlx5enetdevchange_profile can fail to attach a new profile and can fail to rollback to old profile, in such case, we could end up with a dangling netdev with a fully reset…
When was CVE-2026-23000 disclosed?
CVE-2026-23000 was first published in the National Vulnerability Database on January 25, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23000 actively exploited?
CVE-2026-23000 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 95.3% of all scored CVEs.
What is the CVSS score of CVE-2026-23000?
CVE-2026-23000 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23000?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23000, 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

Explore the affected products and dependency analysis for CVE-2026-23000

Explore →

Is Your Infrastructure Affected by CVE-2026-23000?

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

Start Free Scan →Browse All CVEs