md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
06.12.646.18.46.19In the Linux kernel, the following vulnerability has been resolved:
md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()
The variable mddev->private is first assigned to conf and then checked:
conf = mddev->private; if (!conf) ...
If conf is NULL, then mddev->private is also NULL. In this case, null-pointer dereferences can occur when calling raid5_quiesce():
raid5_quiesce(mddev, true); raid5_quiesce(mddev, false);
since mddev->private is assigned to conf again in raid5_quiesce(), and conf is dereferenced in several places, for example:
conf->quiesce = 0; wake_up(&conf->wait_for_quiescent);
From the CVE record · Linux
The Linux kernel’s md/raid5 code can dereference a null pointer when raid5_store_group_thread_cnt() calls raid5_quiesce() while mddev->private is NULL. The input does not specify whether an attacker can trigger this condition, or any required access or user interaction.
Engineers running Linux kernels with md/raid5 should check their versions against the vendor advisory; affected versions are not specified in the input.