zram: set default primary compressor in zram_destroy_comps()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
c4e5683c3031a33dc46954e99d37cbd2f706cdb6| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
Resetting zram compressors can leave the primary compressor NULL. A subsequent read of the compression algorithm can pass that NULL value to strcmp(), potentially causing a kernel NULL pointer dereference. The input does not specify the access requirements for triggering this condition.
Operators running Linux kernels with zram should check their exposure; affected versions are not specified.