nvdimm/bus: Fix potential use after free in asynchronous initialization
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b6eae0f61db27748606cc00dafcfd1e2c032f0a5 · < a226e5b49e5fe8c98b14f8507de670189d191348| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvdimm/bus: Fix potential use after free in asynchronous initialization
Dingisoul with KASAN reports a use after free if device_add() fails in nd_async_device_register().
Commit b6eae0f61db2 ("libnvdimm: Hold reference on parent while scheduling async init") correctly added a reference on the parent device to be held until asynchronous initialization was complete. However, if device_add() results in an allocation failure the ref count of the device drops to 0 prior to the parent pointer being accessed. Thus resulting in use after free.
The bug bot AI correctly identified the fix. Save a reference to the parent pointer to be used to drop the parent reference regardless of the outcome of device_add().
From the CVE record · Linux
The Linux kernel's nvdimm/bus asynchronous initialization has a use-after-free if device_add() fails because of an allocation failure. This can cause the kernel to access a freed device; the input does not specify an attacker route, authentication requirements, or user interaction.
Teams running Linux kernels with the affected nvdimm/bus code should check their kernel version; affected versions are not specified.