CVE-2026-43013

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-01. 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/mlx5: lag: Check for LAG device before creating debugfs

__mlx5_lag_dev_add_mdev() may return 0 (success) even when an error occurs that is handled gracefully. Consequently, the initialization flow proceeds to call mlx5_ldev_add_debugfs() even when there is no valid LAG context.

mlx5_ldev_add_debugfs() blindly created the debugfs directory and attributes. This exposed interfaces (like the members file) that rely on a valid ldev pointer, leading to potential NULL pointer dereferences if accessed when ldev is NULL.

Add a check to verify that mlx5_lag_dev(dev) returns a valid pointer before attempting to create the debugfs entries.

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
2%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 7, 2026

Advisory Details (6)

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

net/mlx5: lag: Check for LAG device before creating debugfs - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5: lag: Check for LAG device before creating debugfs - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5: lag: Check for LAG device before creating debugfs - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5: lag: Check for LAG device before creating debugfs - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5: lag: Check for LAG device before creating debugfs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89c65f2fcd8801365b410f40a427cbcd7f4c28e9
generic

net/mlx5: lag: Check for LAG device before creating debugfs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7129632cab3e4d23510b21930aa73b8d97a859f5

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1056.57~22.04.2) @ jammy2026-08-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1059.62~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (6.8.0-1061.62~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
linuxKernel @ 6.1.168—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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
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 (125 versions)6.19.12-1—

Weakness Classification(1)

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

All Vendor Advisories

(14)

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 / 31× 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 181 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43013?
CVE-2026-43013 is a medium vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: net/mlx5: lag: Check for LAG device before creating debugfs mlx5lagdevaddmdev() may return 0 (success) even when an error occurs that is handled gracefully. Consequently, the initialization flow proceeds to call…
When was CVE-2026-43013 disclosed?
CVE-2026-43013 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43013 actively exploited?
CVE-2026-43013 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 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-43013?
CVE-2026-43013 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43013, 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-43013

Explore →

Is Your Infrastructure Affected by CVE-2026-43013?

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

Start Free Scan →Browse All CVEs