Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43013net/mlx5: lag: Check for LAG device before creating debugfs

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43013, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 7f46a0b7327ae261f9981888708dbca22c283900 – < a3db46d5f4df92630a96f7bc77b60e75c2353e06
    • affected 7f46a0b7327ae261f9981888708dbca22c283900 – < 7129632cab3e4d23510b21930aa73b8d97a859f5
    • affected 7f46a0b7327ae261f9981888708dbca22c283900 – < cfa774e6c920c81e700327bf10db8cb50d5db456
    • affected 7f46a0b7327ae261f9981888708dbca22c283900 – < c53cf44588a93000f71817a6bb87a66353c48dee
    • affected 7f46a0b7327ae261f9981888708dbca22c283900 – < 89c65f2fcd8801365b410f40a427cbcd7f4c28e9
    • affected 7f46a0b7327ae261f9981888708dbca22c283900 – < bf16bca6653679d8a514d6c1c5a2c67065033f14
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.134 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43013 badge
[![CVE-2026-43013](https://cveledger.app/badge/CVE-2026-43013.svg)](https://cveledger.app/cve/CVE-2026-43013)

Record last updated .