Strix
73.3K

CVE-2026-99037

UnknownEPSS 0.17%

Last modified

CVE-2026-99037 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.17%

6.2th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < a04546fa65cbcf4a2774f93f365d747a19abb9b8; >= 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < 412d1c1f490ed9ec5bd029883e8a626626613a70; >= 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < a50e830ded5a0d0cb9e897d1521716ba654f8c3e; >= 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < 9a0dab8a9d9975dec14a118b55cae2517aea5ca9; >= 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < 962ce265fbf5d87afeb78cf19c12e083ab0ffeb8; >= 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < a1a875614dae43b43d311bb9e7a7a70eed78efe6; >= 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < 40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f; >= 33d2f09fcb357fd1861c4959d1d3505492bf91f8, < 3195e0daf590683992edb4eed32269e569e04924
LinuxLinux4.12

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-99037?
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.
How severe is CVE-2026-99037?
Severity scoring for CVE-2026-99037 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-99037?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-99037?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST