rbd: avoid use-after-free in do_rbd_add() when rbd_dev_create() fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1643dfa4c2c827d6e2aa419df8c17b0f24090278 · < faa7b683e436664fff5648426950718277831348| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
rbd: avoid use-after-free in do_rbd_add() when rbd_dev_create() fails
If getting an ID or setting up a work queue in rbd_dev_create() fails, use-after-free on rbd_dev->rbd_client, rbd_dev->spec and rbd_dev->opts is triggered in do_rbd_add(). The root cause is that the ownership of these structures is transfered to rbd_dev prematurely and they all end up getting freed when rbd_dev_create() calls rbd_dev_free() prior to returning to do_rbd_add().
Found by Linux Verification Center (linuxtesting.org) with SVACE, an incomplete patch submitted by Natalia Petrova <n.petrova@fintech.ru>.
From the CVE record · Linux
The Linux kernel’s rbd code has a use-after-free in do_rbd_add() if rbd_dev_create() fails while obtaining an ID or setting up a work queue. The input does not establish whether an attacker can trigger the failure, what access they would need, or whether user interaction is required.
Engineers running Linux kernels with the rbd component should check their exposure; affected versions are not specified.