From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89717: zram: set default primary compressor in zram_destroy_comps()
Date: Fri, 11 Sep 2026 21:46:46 +0200 [thread overview]
Message-ID: <2026091159-CVE-2026-89717-389b@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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().
The Linux kernel CVE team has assigned CVE-2026-89717 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit 486fd58af7ac1098b68370b1d4d9f94a2a1c7124 and fixed in 6.18.51 with commit 5cec3e60e9f2d1324179df3aa91656f90095cf8f
Issue introduced in 6.12 with commit 486fd58af7ac1098b68370b1d4d9f94a2a1c7124 and fixed in 7.2.4 with commit dea8f13c3dfad8b990f8ea96c997aabeebbc1d22
Issue introduced in 6.12 with commit 486fd58af7ac1098b68370b1d4d9f94a2a1c7124 and fixed in 7.3-rc1 with commit dde75313eed0b014c437f48dd75c0308b592cbf9
Issue introduced in 6.6.57 with commit 6e20720b12299595154857fa98222729f0d5823c
Issue introduced in 6.11.4 with commit c4e5683c3031a33dc46954e99d37cbd2f706cdb6
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-89717
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/block/zram/zram_drv.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/5cec3e60e9f2d1324179df3aa91656f90095cf8f
https://git.kernel.org/stable/c/dea8f13c3dfad8b990f8ea96c997aabeebbc1d22
https://git.kernel.org/stable/c/dde75313eed0b014c437f48dd75c0308b592cbf9
reply other threads:[~2026-09-11 20:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091159-CVE-2026-89717-389b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox