PT-2026-122014
CVE-2026-99037
·
Published
2026-10-23
·
Updated
2026-10-23
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
dm-crypt: reject the lmk IV mode with AEAD ciphers
A "capi:" table line that pairs an AEAD cipher with the lmk IV mode,
for example "capi:gcm(aes)-lmk" with the integrity:28:aead option,
causes an oops when it is loaded. lmk sets tfms count to 64, but
crypt alloc tfms aead only allocates one transform, so crypt setkey
reads past the end of the tfms aead array and calls crypto aead setkey
on the values it finds there.
lmk exists for compatibility with Loop-AES, which uses CBC, so refuse
it with an AEAD cipher rather than allocate 64 AEAD transforms. The
check cannot go in crypt iv lmk ctr with the other lmk checks, because
the IV constructor runs after crypt set key.
Note that this is not a security bug because the memory corruption can
only be triggered by root.
Found an issue in the description? Have something to add? Feel free to write us 👾