x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails
In mce_threshold_create_device(), if threshold_create_bank() fails, the previously allocated threshold banks array @bp will be leaked because the call to mce_threshold_remove_device() will not free it.
This happens because mce_threshold_remove_device() fetches the pointer through the threshold_banks per-CPU variable but bp is written there only after the bank creation is successful, and not before, when threshold_create_bank() fails.
Add a helper which unwinds all the bank creation work previously done and pass into it the previously allocated threshold banks array for freeing.
[ bp: Massage. ]
From the CVE record · Linux
The Linux kernel leaks a previously allocated threshold banks array if threshold_create_bank() fails during device creation. The input does not describe how an attacker could trigger the failure or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with the x86/AMD MCE threshold bank code should check their versions; affected versions are not specified.