dm-crypt: don't modify the data when using authenticated encryption
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 · < 64ba01a365980755732972523600a961c4266b75| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dm-crypt: don't modify the data when using authenticated encryption
It was said that authenticated encryption could produce invalid tag when the data that is being encrypted is modified [1]. So, fix this problem by copying the data into the clone bio first and then encrypt them inside the clone bio.
This may reduce performance, but it is needed to prevent the user from corrupting the device by writing data with O_DIRECT and modifying them at the same time.
[1] https://lore.kernel.org/all/20240207004723.GA35324@sol.localdomain/T/
From the CVE record · Linux
Linux dm-crypt authenticated encryption can produce an invalid tag if data changes while it is being encrypted. A local user writing with O_DIRECT and modifying the data at the same time can corrupt the device.
Anyone running Linux with dm-crypt authenticated encryption should check their kernel; affected versions are not specified.