dm-integrity: fix a memory leak when rechecking the data
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dm-integrity: fix a memory leak when rechecking the data
Memory for the "checksums" pointer will leak if the data is rechecked after checksum failure (because the associated kfree won't happen due to 'goto skip_io').
Fix this by freeing the checksums memory before recheck, and just use the "checksum_onstack" memory for storing checksum during recheck.
From the CVE record · Linux
The Linux kernel's dm-integrity component leaks checksum memory when it rechecks data after a checksum failure. The input does not specify whether an attacker can trigger this condition, or any network, authentication, or user-interaction requirements.
Engineers running the Linux kernel with dm-integrity should check their installations; affected versions are not specified.