zram: set default primary compressor in zram_destroy_comps() (CVE-2026-89717) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-89717

zram: set default primary compressor in zram_destroy_comps()

Answer in brief

CVE-2026-89717 records a Unknown severity vulnerability in zram: set default primary compressor in zram_destroy_comps(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 11, 2026Updated Sep 11, 2026Source checked Sep 11, 2026First seen by HOL Sep 11, 2026Material review Sep 11, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=486fd58af7ac1098b68370b1d4d9f94a2a1c7124 <5cec3e60e9f2d1324179df3aa91656f90095cf8f \|\| >=486fd58af7ac1098b68370b1d4d9f94a2a1c7124 <dea8f13c3dfad8b990f8ea96c997aabeebbc1d22 \|\| >=486fd58af7ac1098b68370b1d4d9f94a2a1c7124 <dde75313eed0b014c437f48dd75c0308b592cbf9 \|\| 6e20720b12299595154857fa98222729f0d5823c \|\| c4e5683c3031a33dc46954e99d37cbd2f706cdb6 \|\| >=6.6.57 <6.7 \|\| >=6.11.4 <6.12	5cec3e60e9f2d1324179df3aa91656f90095cf8f, dea8f13c3dfad8b990f8ea96c997aabeebbc1d22, dde75313eed0b014c437f48dd75c0308b592cbf9, 6.7, 6.12
Linux/Linuxgeneric	6.12	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 5cec3e60e9f2d1324179df3aa91656f90095cf8f if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 11, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: zram: set default primary compressor in zram_destroy_comps() Patch series "zram: fix zram issues reported by sashiko". Sashiko drove by and reported [1] a couple of zram issues: a possible BUG_ON() in zlib code due to missing winbits range validation and one possible NULL-ptr dereference in zcomp. Both are low risk yet still worth fixing. This patch (of 2): zram_destroy_comps() resets all compressors and leaves them set to NULL, including the primary one, which is invalid device state, as now comp_algorithm_show()->strcmp() can be called on a NULL compressor. Set default primary compressor in zram_destroy_comps().

Quoted source text, attributed separately from HOL analysis.