module: ensure that kobject_put() is safe for module type kobjects
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 942e443127e928a5631c3d5102aca8c8b3c2dd98 · < d63851049f412cdfadaeef7a7eaef5031d11c1e9| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's module kobject error-handling path can use an uninitialized completion pointer when it calls kobject_put(). The input does not specify an attacker outcome or whether exploitation requires network access, local access, authentication, or user interaction.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.