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.
Metrics
Affected Vendors & Products
References
History
Wed, 04 Jun 2025 13:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Fri, 30 May 2025 21:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Thu, 29 May 2025 13:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
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. | |
Title | module: ensure that kobject_put() is safe for module type kobjects | |
References |
|
|

Status: PUBLISHED
Assigner: Linux
Published:
Updated: 2025-06-04T12:57:43.549Z
Reserved: 2025-04-16T04:51:23.976Z
Link: CVE-2025-37995

No data.

Status : Awaiting Analysis
Published: 2025-05-29T14:15:36.043
Modified: 2025-06-04T13:15:28.403
Link: CVE-2025-37995
