Vulnerability feed

Executive summary

The advisory describes a flaw in the Linux kernel's dm-crypt device-mapper component. A crafted table line pairing an AEAD cipher with the lmk IV mode causes a kernel oops when loaded, and the advisory states it can only be triggered by root. The advisory does not state a severity score, and the fix is a kernel commit that rejects this combination.

Technical summary

The flaw is a memory corruption issue in dm-crypt: setting tfms_count to 64 for the lmk IV mode while only one AEAD transform is allocated causes crypt_setkey to read past the end of the tfms_aead array and call crypto_aead_setkey on invalid values. The attack requires local root to load a capi: table line such as capi:gcm(aes)-lmk with the integrity:28:aead option, and the advisory states it is not a security bug for that reason. The fix adds a check in crypt_ctr_cipher_new that rejects lmk with AEAD ciphers, and the advisory references the commit 3195e0daf590683992edb4eed32269e569e04924. Affected kernel versions and fixed release versions are not stated in the advisory. No workaround beyond the patch is stated, and no detection guidance or exploitation status is stated.

Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source.

Summarized from git.kernel.org/stable/c/3195e0daf590683…b4eed32269e569e04924

Score

No CVSS score published.

Affects

LinuxLinuxLinux kernelLinux dm-crypt