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-98217IB/mlx4: Fix use-after-free on pkey sysfs registration failure

Description

In the Linux kernel, the following vulnerability has been resolved: IB/mlx4: Fix use-after-free on pkey sysfs registration failure register_pkey_tree() ignores errors from register_one_pkey_tree() and continues registering the remaining slaves. The per-slave error path has already released the pkey parent kobjects, but their pointers remain stored in the device. A later device cleanup therefore passes the stale pointers to kobject_put(), causing a use-after-free. Clear the parent pointers after releasing a failed slave tree and skip unregistered trees during device cleanup. This preserves the existing best-effort registration behavior while preventing a second cleanup of the failed tree.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected c1e7e466120b80ce49e91af0c9da1ce6dee4844a – < 791471421d848ce13e84f4b21c9e19973d471c4e
    • affected c1e7e466120b80ce49e91af0c9da1ce6dee4844a – < 734f066933484f6c7cedea0312763249beed5845
    • affected c1e7e466120b80ce49e91af0c9da1ce6dee4844a – < a07bee32127d7c4cd3b1bb9a088e21d0c93634c9
    • affected c1e7e466120b80ce49e91af0c9da1ce6dee4844a – < cf20d7476754c00eec04ae23d3e929de33ce0345
    • affected c1e7e466120b80ce49e91af0c9da1ce6dee4844a – < 0c3482e965b18bc242e54e899d1c4d391ca8e5e3
    • affected c1e7e466120b80ce49e91af0c9da1ce6dee4844a – < ffb80872617b5f9b3dd1536ec2909029fa66f228
    • affected c1e7e466120b80ce49e91af0c9da1ce6dee4844a – < ced1186fea7c77e16681c7ef4802897885989c3b
    • affected c1e7e466120b80ce49e91af0c9da1ce6dee4844a – < 1af874e9f4ce22ccf8b10ab5462f32c70d3be21a
  • Linux · Linux

    • affected 3.7
    • unaffected < 3.7
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .