dm-thin: fix metadata refcount underflow
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3241b1d3e0aaafbfcd320f4d71ade629728cc4f4 · < 85311a585a26640760cd0f3349ab9f2905691044| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dm-thin: fix metadata refcount underflow
There's a bug in dm-thin in the function rebalance_children. If the internal btree node has one entry, the code tries to copy all btree entries from the node's child to the node itself and then decrement the child's reference count.
If the child node is shared (it has reference count > 1), we won't free it, so there would be two pointers to each of the grandchildren nodes. But the reference counts of the grandchildren is not increased, thus the reference count doesn't match the number of pointers that point to the grandchildren. This results in "device mapper: space map common: unable to decrement block" errors.
Fix this bug by incrementing reference counts on the grandchildren if the btree node is shared.
From the CVE record · Linux
A bug in the Linux kernel’s dm-thin metadata handling can leave reference counts inconsistent when a shared btree child node is rebalanced. This can cause “unable to decrement block” errors; the input does not specify how an attacker could trigger the bug or whether authentication or user interaction is required.
Engineers running Linux kernels with dm-thin should check their exposure; affected versions are not specified.