https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 26 Oct 2026 11:37:40 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-99037 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm-crypt: reject the lmk IV mode with AEAD ciphers</p> <p>A &#34;capi:&#34; table line that pairs an AEAD cipher with the lmk IV mode, for example &#34;capi:gcm(aes)-lmk&#34; 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.</p> <p>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.</p> <p>Note that this is not a security bug because the memory corruption can only be triggered by root.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm-crypt: reject the lmk IV mode with AEAD ciphers</p> <p>A &#34;capi:&#34; table line that pairs an AEAD cipher with the lmk IV mode, for example &#34;capi:gcm(aes)-lmk&#34; 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.</p> <p>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.</p> <p>Note that this is not a security bug because the memory corruption can only be triggered by root.</p> https://db.gcve.eu/vuln/fkie_cve-2026-99037 https://db.gcve.eu/vuln/ghsa-9xmg-p5vw-vprw <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm-crypt: reject the lmk IV mode with AEAD ciphers</p> <p>A &#34;capi:&#34; table line that pairs an AEAD cipher with the lmk IV mode, for example &#34;capi:gcm(aes)-lmk&#34; 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.</p> <p>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.</p> <p>Note that this is not a security bug because the memory corruption can only be triggered by root.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm-crypt: reject the lmk IV mode with AEAD ciphers</p> <p>A &#34;capi:&#34; table line that pairs an AEAD cipher with the lmk IV mode, for example &#34;capi:gcm(aes)-lmk&#34; 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.</p> <p>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.</p> <p>Note that this is not a security bug because the memory corruption can only be triggered by root.</p> https://db.gcve.eu/vuln/ghsa-9xmg-p5vw-vprw https://db.gcve.eu/vuln/msrc_cve-2026-99037 msrc_CVE-2026-99037 https://db.gcve.eu/vuln/msrc_cve-2026-99037