Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99037dm-crypt: reject the lmk IV mode with AEAD ciphers

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.

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 – < a04546fa65cbcf4a2774f93f365d747a19abb9b8
    • affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 – < 412d1c1f490ed9ec5bd029883e8a626626613a70
    • affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 – < a50e830ded5a0d0cb9e897d1521716ba654f8c3e
    • affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 – < 9a0dab8a9d9975dec14a118b55cae2517aea5ca9
    • affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 – < 962ce265fbf5d87afeb78cf19c12e083ab0ffeb8
    • affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 – < a1a875614dae43b43d311bb9e7a7a70eed78efe6
    • affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 – < 40ea7dfa8cd5f9aed72a55c9ca3008aee5880e6f
    • affected 33d2f09fcb357fd1861c4959d1d3505492bf91f8 – < 3195e0daf590683992edb4eed32269e569e04924
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99037 badge
[![CVE-2026-99037](https://cveledger.app/badge/CVE-2026-99037.svg)](https://cveledger.app/cve/CVE-2026-99037)

Record last updated .