Skip to main content
VulnerabilityPublished

CVE-2026-99037: Linux kernel · dm-crypt: reject the lmk IV mode with AEAD ciphers

Source GCVE Database

0
Authoritative record:CVE-2026-99037· Low

Not known to be exploited · fixed in a1a875614dae43b43d311bb9e7a7a70eed78efe6 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity
Low

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

  1. Disclosed: evidence found.

    CVE published 23 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < a1a875614dae43b43d311bb9e7a7a70eed78efe6
Fixed in
  • a1a875614dae43b43d311bb9e7a7a70eed78efe6
LinuxLinuxAffected
  • ≥ 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < 3195e0daf590683992edb4eed32269e569e04924
Fixed in
  • 3195e0daf590683992edb4eed32269e569e04924
LinuxLinuxAffected
  • ≥ 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < 962ce265fbf5d87afeb78cf19c12e083ab0ffeb8
Fixed in
  • 962ce265fbf5d87afeb78cf19c12e083ab0ffeb8
LinuxLinuxAffected
  • ≥ 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < 40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f
Fixed in
  • 40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f
LinuxLinuxAffected
  • ≥ 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < 9a0dab8a9d9975dec14a118b55cae2517aea5ca9
Fixed in
  • 9a0dab8a9d9975dec14a118b55cae2517aea5ca9
LinuxLinuxAffected
  • =4.12
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

Community reviews

Loading reviews…