First published: Wed Apr 03 2024(Updated: )
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/
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.119-1 6.12.11-1 6.12.12-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-26763 is classified as a medium severity vulnerability due to the potential for data integrity issues.
To mitigate CVE-2024-26763, update the Linux kernel to a safe version such as 5.10.223-1, 5.10.226-1, 6.1.119-1, 6.1.123-1, 6.12.11-1, or 6.12.12-1.
CVE-2024-26763 addresses issues with the dm-crypt implementation that could lead to invalid tag production when authenticated encryption is performed on modified data.
CVE-2024-26763 affects systems running vulnerable versions of the Linux kernel, notably those using the dm-crypt module.
CVE-2024-26763 is not considered remotely exploitable as it requires local access to the affected system to exploit the vulnerability.