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-2025-22126md: fix mddev uaf while iterating all_mddevs list

Description

In the Linux kernel, the following vulnerability has been resolved: md: fix mddev uaf while iterating all_mddevs list While iterating all_mddevs list from md_notify_reboot() and md_exit(), list_for_each_entry_safe is used, and this can race with deletint the next mddev, causing UAF: t1: spin_lock //list_for_each_entry_safe(mddev, n, ...) mddev_get(mddev1) // assume mddev2 is the next entry spin_unlock t2: //remove mddev2 ... mddev_free spin_lock list_del spin_unlock kfree(mddev2) mddev_put(mddev1) spin_lock //continue dereference mddev2->all_mddevs The old helper for_each_mddev() actually grab the reference of mddev2 while holding the lock, to prevent from being freed. This problem can be fixed the same way, however, the code will be complex. Hence switch to use list_for_each_entry, in this case mddev_put() can free the mddev1 and it's not safe as well. Refer to md_seq_show(), also factor out a helper mddev_put_locked() to fix this problem.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 13 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-2025-22126, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected f26514342255855f4ca3c0a92cb1cdea01c33004 – < ca9f84de76723b358dfc0606668efdca54afc2e5
    • affected f26514342255855f4ca3c0a92cb1cdea01c33004 – < d69a23d8e925f8052d657652a6875ec2712c7e33
    • affected f26514342255855f4ca3c0a92cb1cdea01c33004 – < e2a9f73ee408a460f4c9dfe03b4741d6b11652b8
    • affected f26514342255855f4ca3c0a92cb1cdea01c33004 – < 5462544ccbad3fc938a71b01fa5bd3a0dc2b750a
    • affected f26514342255855f4ca3c0a92cb1cdea01c33004 – < 8542870237c3a48ff049b6c5df5f50c8728284fa
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.135 – ≤ 6.1.*
    • unaffected 6.6.88 – ≤ 6.6.*
    • unaffected 6.12.25 – ≤ 6.12.*
    • unaffected 6.14.2 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .