x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 396b8e7ab2a99ddac57d3522b3da5e58cb608d37, Kernel 9708f1956eeb70c86943e0bc62fa3b0101b59616, Kernel b4acb8e7f1594607bc9017ef0aacb40b24a003d6 and 2 more.
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. ]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.8, >=6458de97fc15530b54477c4e2b70af653e8ac3d9 <396b8e7ab2a99ddac57d3522b3da5e58cb608d37, >=6458de97fc15530b54477c4e2b70af653e8ac3d9 <9708f1956eeb70c86943e0bc62fa3b0101b59616, >=6458de97fc15530b54477c4e2b70af653e8ac3d9 <b4acb8e7f1594607bc9017ef0aacb40b24a003d6, >=6458de97fc15530b54477c4e2b70af653e8ac3d9 <cc0dd4456f9573bf8af9b4d8754433918e809e1e, >=6458de97fc15530b54477c4e2b70af653e8ac3d9 <e5f28623ceb103e13fc3d7bd45edf9818b227fd0 | 396b8e7ab2a99ddac57d3522b3da5e58cb608d37, 9708f1956eeb70c86943e0bc62fa3b0101b59616, b4acb8e7f1594607bc9017ef0aacb40b24a003d6, cc0dd4456f9573bf8af9b4d8754433918e809e1e, e5f28623ceb103e13fc3d7bd45edf9818b227fd0 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket