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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 3
- StatusReceived → PublishedNVD modified 2026-10-23 12:21
- StatusPublished → ReceivedNVD modified 2026-10-23 13:17
- First seenunscored · linuxNVD modified 2026-10-23 12:21
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://git.kernel.org/stable/c/3195e0daf590683992edb4eed32269e569e04924
- https://git.kernel.org/stable/c/40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f
- https://git.kernel.org/stable/c/962ce265fbf5d87afeb78cf19c12e083ab0ffeb8
- https://git.kernel.org/stable/c/9a0dab8a9d9975dec14a118b55cae2517aea5ca9
- https://git.kernel.org/stable/c/a1a875614dae43b43d311bb9e7a7a70eed78efe6