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-38313bus: fsl-mc: fix double-free on mc_dev

Description

In the Linux kernel, the following vulnerability has been resolved: bus: fsl-mc: fix double-free on mc_dev The blamed commit tried to simplify how the deallocations are done but, in the process, introduced a double-free on the mc_dev variable. In case the MC device is a DPRC, a new mc_bus is allocated and the mc_dev variable is just a reference to one of its fields. In this circumstance, on the error path only the mc_bus should be freed. This commit introduces back the following checkpatch warning which is a false-positive. WARNING: kfree(NULL) is safe and this check is probably not required + if (mc_bus) + kfree(mc_bus);

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 10 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-38313, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.19% · top 91% of all CVEs (12 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 a042fbed02904493ae6df26ec836045f5a7d3ce2 – < 12e4431e5078847791936820bd39df9e1ee26d2e
    • affected a042fbed02904493ae6df26ec836045f5a7d3ce2 – < 3135e03a92f6b5259d0a7f25f728e9e7866ede3f
    • affected a042fbed02904493ae6df26ec836045f5a7d3ce2 – < 7002b954c4a8b9965ba0f139812ee4a6f71beac8
    • affected a042fbed02904493ae6df26ec836045f5a7d3ce2 – < b2057374f326303c86d8423415ab58656eebc695
    • affected a042fbed02904493ae6df26ec836045f5a7d3ce2 – < 4b23c46eb2d88924b93aca647bde9a4b9cf62cf9
    • affected a042fbed02904493ae6df26ec836045f5a7d3ce2 – < 1d5baab39e5b09a76870b345cdee7933871b881f
    • affected a042fbed02904493ae6df26ec836045f5a7d3ce2 – < 873d47114fd5e5a1cad2018843671537cc71ac84
    • affected a042fbed02904493ae6df26ec836045f5a7d3ce2 – < d694bf8a9acdbd061596f3e7549bc8cb70750a60
  • Linux · Linux

    • affected 4.13
    • unaffected < 4.13
    • unaffected 5.4.295 – ≤ 5.4.*
    • unaffected 5.10.239 – ≤ 5.10.*
    • unaffected 5.15.186 – ≤ 5.15.*
    • unaffected 6.1.142 – ≤ 6.1.*
    • unaffected 6.6.94 – ≤ 6.6.*
    • unaffected 6.12.34 – ≤ 6.12.*
    • unaffected 6.15.3 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .