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-89552

params: fix charp corruption on allocation failure

Description

In the Linux kernel, the following vulnerability has been resolved: params: fix charp corruption on allocation failure param_set_charp() stores charp parameters in allocated memory after slab is available, and releases the previous value when the parameter is updated. The previous value is released before the replacement allocation succeeds. If kmalloc_parameter() fails, the setter returns -ENOMEM with the parameter left as NULL. Failing zswap's compressor update before zswap is initialized can later trigger: BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:strcmp+0x10/0x30 Call Trace: zswap_setup+0x3b1/0x490 zswap_enabled_param_set+0x5b/0xa0 param_attr_store+0x93/0xe0 module_attr_store+0x1c/0x30 kernfs_fop_write_iter+0x116/0x1f0 Allocate and copy the replacement first, then replace the parameter value only after allocation succeeds.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 49 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 (12 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 e180a6b7759a99a28cbcce3547c4c80822cb6c2a – < 72835d539ed3eb4c4b85b85a3f3976c7bdc70b91
    • affected e180a6b7759a99a28cbcce3547c4c80822cb6c2a – < c7cc1edf3c0de948abcb3e4a44ee86a82403ce2f
    • affected e180a6b7759a99a28cbcce3547c4c80822cb6c2a – < 32c1f305cfad192cd98468140beedeffe4792f53
    • affected e180a6b7759a99a28cbcce3547c4c80822cb6c2a – < 31b41ea8383d51992d6b0dfe3a99da1dec8ce1c1
    • affected e180a6b7759a99a28cbcce3547c4c80822cb6c2a – < 614f873268c5b172804c9af6639bd17b7e1e2359
    • affected e180a6b7759a99a28cbcce3547c4c80822cb6c2a – < 704ecd010d4a9b33160e40b74eb402f6b86a18e0
    • affected e180a6b7759a99a28cbcce3547c4c80822cb6c2a – < 0d8e2404925a0607ffec79a53170715a46936896
    • affected e180a6b7759a99a28cbcce3547c4c80822cb6c2a – < 3dfaae04243cde460d82dfc2a7dd0bb6664d20ae
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • 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.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 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-89552 badge
[![CVE-2026-89552](https://cveledger.app/badge/CVE-2026-89552.svg)](https://cveledger.app/cve/CVE-2026-89552)

Record last updated .