CVE-2026-89552 — params: fix charp corruption on allocation failure
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ e180a6b7759a99a28cbcce3547c4c80822cb6c2a and < 614f873268c5b172804c9af6639bd17b7e1e2359≥ e180a6b7759a99a28cbcce3547c4c80822cb6c2a and < 704ecd010d4a9b33160e40b74eb402f6b86a18e0≥ e180a6b7759a99a28cbcce3547c4c80822cb6c2a and < 0d8e2404925a0607ffec79a53170715a46936896≥ e180a6b7759a99a28cbcce3547c4c80822cb6c2a and < 3dfaae04243cde460d82dfc2a7dd0bb6664d20aeversion 2.6.30≥ e180a6b7759a99a28cbcce3547c4c80822cb6c2a and < 31b41ea8383d51992d6b0dfe3a99da1dec8ce1c1 | Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 24, 2026 · 9 reading(s) · max 0.17%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 19, 2026 – Oct 21, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
7 on the record
- github.com/advisories/GHSA-gmqc-x8hx-2ggc
- git.kernel.org/stable/c/31b41ea8383d51992d6b0dfe3a99da1dec8ce1c1
- git.kernel.org/stable/c/614f873268c5b172804c9af6639bd17b7e1e2359
- git.kernel.org/stable/c/704ecd010d4a9b33160e40b74eb402f6b86a18e0
- nvd.nist.gov/vuln/detail/CVE-2026-89552
- git.kernel.org/stable/c/3dfaae04243cde460d82dfc2a7dd0bb6664d20ae
- git.kernel.org/stable/c/0d8e2404925a0607ffec79a53170715a46936896
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99086 dm-integrity: validate the superblock on resume 2d
- Unknown CVE-2026-99087 dm-integrity: fix NULL pointer dereference when the 'R' flag is used 2d
- Unknown CVE-2026-99080 fs: Free any excess xarray nodes in clear_inode() 2d
- Unknown CVE-2026-99084 readdir: take no inode lock on an immutable directory 2d
- Unknown CVE-2026-99085 sched_ext: Fix CPU hotplug hang when a dying CPU's tasks sit in the BPF scheduler 2d
- Critical CVE-2026-99079 net/mlx5e: Prevent stale XSK buffer release on refill retry 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-89552 is "params: fix charp corruption on allocation failure", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.