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-2024-42098crypto: ecdh - explicitly zeroize private_key

Description

In the Linux kernel, the following vulnerability has been resolved: crypto: ecdh - explicitly zeroize private_key private_key is overwritten with the key parameter passed in by the caller (if present), or alternatively a newly generated private key. However, it is possible that the caller provides a key (or the newly generated key) which is shorter than the previous key. In that scenario, some key material from the previous key would not be overwritten. The easiest solution is to explicitly zeroize the entire private_key array first. Note that this patch slightly changes the behavior of this function: previously, if the ecc_gen_privkey failed, the old private_key would remain. Now, the private_key is always zeroized. This behavior is consistent with the case where params.key is set and ecc_is_key_valid fails.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 22 months 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

CVSS scores of CVE-2024-42098, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 – < 39173b04abda87872b43c331468a4a14f8f05ce8
    • affected 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 – < fd7ef325911eba1b7191b83cb580463242f2090d
    • affected 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 – < 80575b252ab0358b7e93895b2a510beb3cb3f975
    • affected 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 – < d96187eb8e59b572a8e6a68b6a9837a867ea29df
    • affected 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 – < 73e5984e540a76a2ee1868b91590c922da8c24c9
  • Linux · Linux

    • affected 4.8
    • unaffected < 4.8
    • unaffected 5.15.162 – ≤ 5.15.*
    • unaffected 6.1.97 – ≤ 6.1.*
    • unaffected 6.6.37 – ≤ 6.6.*
    • unaffected 6.9.8 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .