{"api_version":"1","generated_at":"2026-10-24T10:56:09+00:00","cve":"CVE-2026-99037","urls":{"html":"https://cve.report/CVE-2026-99037","api":"https://cve.report/api/cve/CVE-2026-99037.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99037","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99037"},"summary":{"title":"dm-crypt: reject the lmk IV mode with AEAD ciphers","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndm-crypt: reject the lmk IV mode with AEAD ciphers\n\nA \"capi:\" table line that pairs an AEAD cipher with the lmk IV mode,\nfor example \"capi:gcm(aes)-lmk\" with the integrity:28:aead option,\ncauses an oops when it is loaded. lmk sets tfms_count to 64, but\ncrypt_alloc_tfms_aead only allocates one transform, so crypt_setkey\nreads past the end of the tfms_aead array and calls crypto_aead_setkey\non the values it finds there.\n\nlmk exists for compatibility with Loop-AES, which uses CBC, so refuse\nit with an AEAD cipher rather than allocate 64 AEAD transforms. The\ncheck cannot go in crypt_iv_lmk_ctr with the other lmk checks, because\nthe IV constructor runs after crypt_set_key.\n\nNote that this is not a security bug because the memory corruption can\nonly be triggered by root.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-23 13:17:26","updated_at":"2026-10-23 13:17:26"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/962ce265fbf5d87afeb78cf19c12e083ab0ffeb8","name":"https://git.kernel.org/stable/c/962ce265fbf5d87afeb78cf19c12e083ab0ffeb8","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/3195e0daf590683992edb4eed32269e569e04924","name":"https://git.kernel.org/stable/c/3195e0daf590683992edb4eed32269e569e04924","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a1a875614dae43b43d311bb9e7a7a70eed78efe6","name":"https://git.kernel.org/stable/c/a1a875614dae43b43d311bb9e7a7a70eed78efe6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f","name":"https://git.kernel.org/stable/c/40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9a0dab8a9d9975dec14a118b55cae2517aea5ca9","name":"https://git.kernel.org/stable/c/9a0dab8a9d9975dec14a118b55cae2517aea5ca9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99037","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99037","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 9a0dab8a9d9975dec14a118b55cae2517aea5ca9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 962ce265fbf5d87afeb78cf19c12e083ab0ffeb8 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 a1a875614dae43b43d311bb9e7a7a70eed78efe6 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 3195e0daf590683992edb4eed32269e569e04924 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.12","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.12 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.160 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.113 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.57 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.11 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/md/dm-crypt.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"9a0dab8a9d9975dec14a118b55cae2517aea5ca9","status":"affected","version":"33d2f09fcb357fd1861c4959d1d3505492bf91f8","versionType":"git"},{"lessThan":"962ce265fbf5d87afeb78cf19c12e083ab0ffeb8","status":"affected","version":"33d2f09fcb357fd1861c4959d1d3505492bf91f8","versionType":"git"},{"lessThan":"a1a875614dae43b43d311bb9e7a7a70eed78efe6","status":"affected","version":"33d2f09fcb357fd1861c4959d1d3505492bf91f8","versionType":"git"},{"lessThan":"40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f","status":"affected","version":"33d2f09fcb357fd1861c4959d1d3505492bf91f8","versionType":"git"},{"lessThan":"3195e0daf590683992edb4eed32269e569e04924","status":"affected","version":"33d2f09fcb357fd1861c4959d1d3505492bf91f8","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/md/dm-crypt.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.12"},{"lessThan":"4.12","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.160","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.113","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.57","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.11","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.160","versionStartIncluding":"4.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.113","versionStartIncluding":"4.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.57","versionStartIncluding":"4.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.11","versionStartIncluding":"4.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"4.12","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndm-crypt: reject the lmk IV mode with AEAD ciphers\n\nA \"capi:\" table line that pairs an AEAD cipher with the lmk IV mode,\nfor example \"capi:gcm(aes)-lmk\" with the integrity:28:aead option,\ncauses an oops when it is loaded. lmk sets tfms_count to 64, but\ncrypt_alloc_tfms_aead only allocates one transform, so crypt_setkey\nreads past the end of the tfms_aead array and calls crypto_aead_setkey\non the values it finds there.\n\nlmk exists for compatibility with Loop-AES, which uses CBC, so refuse\nit with an AEAD cipher rather than allocate 64 AEAD transforms. The\ncheck cannot go in crypt_iv_lmk_ctr with the other lmk checks, because\nthe IV constructor runs after crypt_set_key.\n\nNote that this is not a security bug because the memory corruption can\nonly be triggered by root."}],"providerMetadata":{"dateUpdated":"2026-10-23T12:21:54.317Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/9a0dab8a9d9975dec14a118b55cae2517aea5ca9"},{"url":"https://git.kernel.org/stable/c/962ce265fbf5d87afeb78cf19c12e083ab0ffeb8"},{"url":"https://git.kernel.org/stable/c/a1a875614dae43b43d311bb9e7a7a70eed78efe6"},{"url":"https://git.kernel.org/stable/c/40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f"},{"url":"https://git.kernel.org/stable/c/3195e0daf590683992edb4eed32269e569e04924"}],"title":"dm-crypt: reject the lmk IV mode with AEAD ciphers","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99037","datePublished":"2026-10-23T12:21:54.317Z","dateReserved":"2026-09-25T10:25:14.387Z","dateUpdated":"2026-10-23T12:21:54.317Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-23 13:17:26","lastModifiedDate":"2026-10-23 13:17:26","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99037","Ordinal":"1","Title":"dm-crypt: reject the lmk IV mode with AEAD ciphers","CVE":"CVE-2026-99037","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99037","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ndm-crypt: reject the lmk IV mode with AEAD ciphers\n\nA \"capi:\" table line that pairs an AEAD cipher with the lmk IV mode,\nfor example \"capi:gcm(aes)-lmk\" with the integrity:28:aead option,\ncauses an oops when it is loaded. lmk sets tfms_count to 64, but\ncrypt_alloc_tfms_aead only allocates one transform, so crypt_setkey\nreads past the end of the tfms_aead array and calls crypto_aead_setkey\non the values it finds there.\n\nlmk exists for compatibility with Loop-AES, which uses CBC, so refuse\nit with an AEAD cipher rather than allocate 64 AEAD transforms. The\ncheck cannot go in crypt_iv_lmk_ctr with the other lmk checks, because\nthe IV constructor runs after crypt_set_key.\n\nNote that this is not a security bug because the memory corruption can\nonly be triggered by root.","Type":"Description","Title":"dm-crypt: reject the lmk IV mode with AEAD ciphers"}]}}}