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-37995module: ensure that kobject_put() is safe for module type kobjects

Description

In the Linux kernel, the following vulnerability has been resolved: module: ensure that kobject_put() is safe for module type kobjects In 'lookup_or_create_module_kobject()', an internal kobject is created using 'module_ktype'. So call to 'kobject_put()' on error handling path causes an attempt to use an uninitialized completion pointer in 'module_kobject_release()'. In this scenario, we just want to release kobject without an extra synchronization required for a regular module unloading process, so adding an extra check whether 'complete()' is actually required makes 'kobject_put()' safe.

Timeline

  1. ID reserved

    By Linux

  2. · 43 days later

    Published

  3. · 18 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-37995, 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.22% · top 87% of all CVEs (15 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 942e443127e928a5631c3d5102aca8c8b3c2dd98 – < 93799fb988757cdacf19acba57807746c00378e6
    • affected 942e443127e928a5631c3d5102aca8c8b3c2dd98 – < a63d99873547d8b39eb2f6db79dd235761e7098a
    • affected 942e443127e928a5631c3d5102aca8c8b3c2dd98 – < f1c71b4bd721a4ea21da408806964b10468623f2
    • affected 942e443127e928a5631c3d5102aca8c8b3c2dd98 – < 9e7b49ce4f9d0cb5b6e87db9e07a2fb9e754b0dd
    • affected 942e443127e928a5631c3d5102aca8c8b3c2dd98 – < faa9059631d3491d699c69ecf512de9e1a3d6649
    • affected 942e443127e928a5631c3d5102aca8c8b3c2dd98 – < d63851049f412cdfadaeef7a7eaef5031d11c1e9
    • affected 942e443127e928a5631c3d5102aca8c8b3c2dd98 – < 31d8df3f303c3ae9115230820977ef8c35c88808
    • affected 942e443127e928a5631c3d5102aca8c8b3c2dd98 – < a6aeb739974ec73e5217c75a7c008a688d3d5cf1
  • Linux · Linux

    • affected 3.12
    • unaffected < 3.12
    • unaffected 5.4.294 – ≤ 5.4.*
    • unaffected 5.10.238 – ≤ 5.10.*
    • unaffected 5.15.183 – ≤ 5.15.*
    • unaffected 6.1.139 – ≤ 6.1.*
    • unaffected 6.6.91 – ≤ 6.6.*
    • unaffected 6.12.29 – ≤ 6.12.*
    • unaffected 6.14.7 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .