CVE-2026-99037 json
dm-crypt: reject the lmk IV mode with AEAD ciphers
published 19d ago modified 12d ago also EUVD-2026-108832
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.11-1
debian advisories DEBIAN-CVE-2026-99037
- linux Ubuntu 26.10 7.3.0-10.10
- linux-aws Ubuntu 26.10 7.3.0-1004.4
- linux-gcp Ubuntu 26.10 7.3.0-1004.4
- linux-raspi Ubuntu 26.10 7.3.0-1004.4
- linux-riscv Ubuntu 26.10 7.3.0-10.10.1
- linux-oracle Ubuntu 26.10 7.3.0-1004.4
- linux-realtime Ubuntu 26.10 7.3.0-10.10.1
ubuntu advisories UBUNTU-CVE-2026-99037
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-110906
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/a04546fa65cbcf4a2774f93f365d747a19abb9b8 commit
- git.kernel.org/stable/c/412d1c1f490ed9ec5bd029883e8a626626613a70 commit
- git.kernel.org/stable/c/a50e830ded5a0d0cb9e897d1521716ba654f8c3e commit
- git.kernel.org/stable/c/9a0dab8a9d9975dec14a118b55cae2517aea5ca9 commit
- git.kernel.org/stable/c/962ce265fbf5d87afeb78cf19c12e083ab0ffeb8 commit
- git.kernel.org/stable/c/a1a875614dae43b43d311bb9e7a7a70eed78efe6 commit
- git.kernel.org/stable/c/40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f commit
- git.kernel.org/stable/c/3195e0daf590683992edb4eed32269e569e04924 commit
Is CVE-2026-99037 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99037 updated cvss 4.4
kernel: dm-crypt: reject the lmk IV mode with AEAD ciphers
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/a04546fa65cbcf4a2774f93f365d747a19abb9b8
- git.kernel.org /stable/c/412d1c1f490ed9ec5bd029883e8a626626613a70
- git.kernel.org /stable/c/a50e830ded5a0d0cb9e897d1521716ba654f8c3e
- git.kernel.org /stable/c/9a0dab8a9d9975dec14a118b55cae2517aea5ca9
- git.kernel.org /stable/c/962ce265fbf5d87afeb78cf19c12e083ab0ffeb8
- git.kernel.org /stable/c/a1a875614dae43b43d311bb9e7a7a70eed78efe6
- git.kernel.org /stable/c/40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f
- git.kernel.org /stable/c/3195e0daf590683992edb4eed32269e569e04924
Sources
- CVE List CVE-2026-99037
- NVD CVE-2026-99037
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.