diff options
| author | Mikulas Patocka <mpatocka@redhat.com> | 2026-07-10 14:31:25 +0200 |
|---|---|---|
| committer | Mikulas Patocka <mpatocka@redhat.com> | 2026-07-10 14:38:01 +0200 |
| commit | 24d7e5e39b04c1ef8eee0688ca1527e879b22a40 (patch) | |
| tree | 197f19213fac79a31a64adc533b4d3875643850d /scripts | |
| parent | 8d4dd2db7f4f3af0d3cd51111d050301c1f00a5c (diff) | |
dm-integrity: fix the 'fix_hmac' option
When the "fix_hmac" argument is used, dm-integrity is supposed to check
the superblock with the journal_mac. However, there was a logic bug in
the code - the code only checked the superblock mac if the bit
SB_FLAG_FIXED_HMAC was set in the superblock. So, the attacker could
clear this bit and bypass the checking trivially.
This commit changes dm-integrity so that when the user specified the
"fix_hmac" flag and the superblock doesn't have the bit
SB_FLAG_FIXED_HMAC set, the activation is aborted with an error.
Unfortunatelly, there's a bug in the integritysetup tool that when using
the 'open' command it passes the "fix_hmac" argument to the kernel even
if the user specified --integrity-legacy-hmac. The bug will be fixed in
the upcoming 2.8.7 release.
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Reported-by: Shukai Ni <shukai.ni@kuleuven.be>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
