{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99037 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99037 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99037 and fix it if it is affected.\n\nWhat it is: CVE-2026-99037 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99037 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-99037/ (Markdown: https://insights.sbomify.com/CVE-2026-99037/index.md)","id":"CVE-2026-99037","markdown":"https://insights.sbomify.com/CVE-2026-99037/index.md","name":"CVE-2026-99037","record":{"aliases":["AZL-110906","BELL-CVE-2026-99037","DEBIAN-CVE-2026-99037","GHSA-9xmg-p5vw-vprw","UBUNTU-CVE-2026-99037"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"dm-crypt: reject the lmk IV mode with AEAD ciphers","id":"CVE-2026-99037","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"memstick: rtsx_usb_ms: complete requests after eject instead of dropping them","id":"CVE-2026-99038"},"packages":[],"prev":{"headline":"dm: fix reading free memory in do_resume","id":"CVE-2026-99036"},"products":["Linux"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99037/"}