CVE-2026-99037: Linux
EPSS: 0.2% probability of exploitation activity in the next 30 days.
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.
What to do
The record states a fixed version for each range of affected versions. Update to the one for the range your version is in: a later release on another branch may not have the fix.
- Linux, from 4.12, before 5.10.273: fixed in 5.10.273
- Linux, from 5.11, before 5.15.224: fixed in 5.15.224
- Linux, from 5.16, before 6.1.191: fixed in 6.1.191
- Linux, from 6.2, before 6.6.160: fixed in 6.6.160
- Linux, from 6.7, before 6.12.113: fixed in 6.12.113
- Linux, from 6.13, before 6.18.57: fixed in 6.18.57
- Linux, from 6.19, before 7.2.11: fixed in 7.2.11
Affected products
- Linux Linux: from 4.12, before 5.10.273 (fixed in 5.10.273); from 5.11, before 5.15.224 (fixed in 5.15.224); from 5.16, before 6.1.191 (fixed in 6.1.191); from 6.2, before 6.6.160 (fixed in 6.6.160); from 6.7, before 6.12.113 (fixed in 6.12.113); from 6.13, before 6.18.57 (fixed in 6.18.57); …
Published 2026-10-23. Last modified 2026-10-30.