CVE-2025-37995
module: ensure that kobject_put() is safe for module type kobjects
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.12
References 8
git.kernel.org
- stable/c/93799fb988757cdacf19acba57807746c00378e6
- stable/c/a63d99873547d8b39eb2f6db79dd235761e7098a
- stable/c/f1c71b4bd721a4ea21da408806964b10468623f2
- stable/c/9e7b49ce4f9d0cb5b6e87db9e07a2fb9e754b0dd
- stable/c/faa9059631d3491d699c69ecf512de9e1a3d6649
- stable/c/d63851049f412cdfadaeef7a7eaef5031d11c1e9
- stable/c/31d8df3f303c3ae9115230820977ef8c35c88808
- stable/c/a6aeb739974ec73e5217c75a7c008a688d3d5cf1