CVE-2026-99037: Linux kernel · dm-crypt: reject the lmk IV mode with AEAD ciphers
Source GCVE Database
Not known to be exploited · fixed in a1a875614dae43b43d311bb9e7a7a70eed78efe6 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in a1a875614dae43b43d311bb9e7a7a70eed78efe6, 3195e0daf590683992edb4eed32269e569e04924, 962ce265fbf5d87afeb78cf19c12e083ab0ffeb8 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99037 (opens in a new tab)
- git.kernel.org/stable/c/3195e0daf590683992edb4eed32269e569e04924 (opens in a new tab)
- git.kernel.org/stable/c/40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f (opens in a new tab)
- git.kernel.org/stable/c/962ce265fbf5d87afeb78cf19c12e083ab0ffeb8 (opens in a new tab)
- git.kernel.org/stable/c/9a0dab8a9d9975dec14a118b55cae2517aea5ca9 (opens in a new tab)
- git.kernel.org/stable/c/a1a875614dae43b43d311bb9e7a7a70eed78efe6 (opens in a new tab)