Bug 2369191 (CVE-2025-37995) - CVE-2025-37995 kernel: module: ensure that kobject_put() is safe for module type kobjects
Summary: CVE-2025-37995 kernel: module: ensure that kobject_put() is safe for module t...
Keywords:
Status: NEW
Alias: CVE-2025-37995
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-29 14:01 UTC by OSIDB Bzimport
Modified: 2025-05-29 17:59 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-29 14:01:42 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.