Answer in brief
CVE-2026-99037 records a Unknown severity vulnerability in dm-crypt: reject the lmk IV mode with AEAD ciphers. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=33d2f09fcb357fd1861c4959d1d3505492bf91f8 <9a0dab8a9d9975dec14a118b55cae2517aea5ca9 || >=33d2f09fcb357fd1861c4959d1d3505492bf91f8 <962ce265fbf5d87afeb78cf19c12e083ab0ffeb8 || >=33d2f09fcb357fd1861c4959d1d3505492bf91f8 <a1a875614dae43b43d311bb9e7a7a70eed78efe6 || >=33d2f09fcb357fd1861c4959d1d3505492bf91f8 <40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f || >=33d2f09fcb357fd1861c4959d1d3505492bf91f8 <3195e0daf590683992edb4eed32269e569e04924 | 9a0dab8a9d9975dec14a118b55cae2517aea5ca9, 962ce265fbf5d87afeb78cf19c12e083ab0ffeb8, a1a875614dae43b43d311bb9e7a7a70eed78efe6, 40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f, 3195e0daf590683992edb4eed32269e569e04924 |
| Linux/Linuxgeneric | 4.12 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
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.
Quoted source text, attributed separately from HOL analysis.