CVE-2026-23044: PM: hibernate: Fix crash when freeing invalid crypto compressor
In the Linux kernel, the following vulnerability has been resolved:
PM: hibernate: Fix crash when freeing invalid crypto compressor
When crypto_alloc_acomp() fails, it returns an ERR_PTR value, not NULL.
The cleanup code in save_compressed_image() and load_compressed_image()
unconditionally calls crypto_free_acomp() without checking for ERR_PTR,
which causes crypto_acomp_tfm() to dereference an invalid pointer and
crash the kernel.
This can be triggered when the compression algorithm is unavailable
(e.g., CONFIG_CRYPTO_LZO not enabled).
Fix by adding IS_ERR_OR_NULL() checks before calling crypto_free_acomp()
and acomp_request_free(), similar to the existing kthread_stop() check.
[ rjw: Added 2 empty code lines ]
Security readout for executives and security teams
Plain-English summary
CVE-2026-23044 is a Linux kernel hibernation bug that can crash the system during compressed hibernate save or restore when a required crypto compression component is unavailable. The public record does not provide CVSS, real-world exploitation, or a broad product matrix.
Executive priority
Track this as an availability risk, not a confirmed widespread compromise risk. Prioritize systems where hibernation is used operationally or where kernel crashes have high business impact.
Technical view
The kernel hibernate compression paths call crypto_free_acomp() on an ERR_PTR returned by crypto_alloc_acomp() failure. That invalid free path can dereference an invalid pointer and crash the kernel. The fix adds IS_ERR_OR_NULL() checks before freeing compressor and request objects.
Likely exposure
Exposure appears limited to Linux systems using affected hibernation compression code, especially configurations where the expected compression algorithm is unavailable, such as missing CONFIG_CRYPTO_LZO. Version data in the source is limited and should be mapped through distribution advisories.
Exploitation context
The source describes a crash trigger tied to unavailable compression support during hibernate save or load. CISA KEV status is false, and no cited source states active exploitation or remote attackability.
Researcher notes
The public record gives clear root cause and fix direction but lacks CVSS, CWE, exploit status, and detailed affected-version ranges. Validate exposure through kernel config, hibernation use, and vendor backport metadata.
Mitigation direction
Apply a kernel update containing the referenced stable fixes.
Check Linux distribution advisories for backported fixed package versions.
Verify hibernation compression dependencies match the running kernel configuration.
Use vendor guidance for temporary controls if updates are delayed.
Validation and detection
Identify hosts that allow or rely on Linux hibernation.
Check running kernel versions against vendor fixed-version advisories.
Confirm whether CONFIG_CRYPTO_LZO or required compressor support is enabled.
Review kernel logs for hibernation crashes around compressed image save or load.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23044 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 4, 2026, 16:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.