CVE-2026-89552 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, Linux distribution vendors, and users of Linux-based systems, particularly those who manage or deploy Linux kernel-based systems, should be aware of this vulnerability. They should review and update Linux kernel configurations to ensure zswap is properly initialized and monitor kernel logs for NULL pointer dereference errors. Additionally, Linux kernel developers and maintainers should prioritize patching or fixing

Why it matters

This vulnerability requires attention from Linux kernel developers, maintainers, and users. A NULL pointer dereference can occur when updating the zswap compressor, potentially leading to kernel crashes or instability. The vulnerability can be triggered when the `zswap_enabled_param_set` function is called before zswap is initialized. Verification of Linux kernel versions and configurations is necessary to determine exposure.

• Potential kernel crashes or instability due to NULL pointer dereferences
• Possible denial-of-service (DoS) attacks exploiting the vulnerability
• Need for verification of Linux kernel versions and configurations to determine exposure
• Potential for local privilege escalation or other security impacts require verification

Technical summary

The vulnerability exists in the Linux kernel's handling of zswap compressor updates. When updating the compressor, the kernel fails to properly handle memory allocation failures, leading to a NULL pointer dereference. This can occur when the `zswap_enabled_param_set` function is called before zswap is initialized. The issue arises from the improper handling of memory allocation failures during the update process, which can trigger a kernel NULL pointer dereference. Affected systems include Linux kernel deployments where zswap is used. To mitigate this vulnerability, it is essential to review and update Linux kernel configurations to ensure zswap is properly initialized and to monitor kernel logs for NULL

Defensive priority

Medium

Recommended defensive actions

• Review and update Linux kernel configurations to ensure zswap is properly initialized
• Monitor kernel logs for NULL pointer dereference errors
• Apply patches or updates provided by the Linux kernel maintainers
• Verify Linux kernel versions and configurations to determine exposure
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by the `param_set_charp` function storing charp parameters in allocated memory after slab is available and releasing the previous value when the parameter is updated. If `kmalloc_parameter` fails, the setter returns -ENOMEM with the parameter left as NULL. This can trigger a NULL pointer dereference when `zswap_setup` is called.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.