drivers/base/memory: fix memory block reference leak in poison accounting
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:
drivers/base/memory: fix memory block reference leak in poison accounting
memblk_nr_poison_inc() and memblk_nr_poison_sub() look up a memory block via find_memory_block_by_id(), which acquires a reference to the memory block device.
Both helpers use the returned memory block without dropping that reference, leaking the device reference on each successful lookup. Drop the reference after updating nr_hwpoison.
From the CVE record · Linux
In the Linux kernel, poison-accounting helpers leak a memory block device reference each time they successfully look up a memory block. The input does not specify how an attacker could trigger this, or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their systems; affected versions are not specified.