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().
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 5
- StatusReceived → PublishedNVD modified 2026-10-21 12:48
- References+1 references (now 5)NVD modified 2026-10-21 13:20
- StatusPublished → ReceivedNVD modified 2026-10-21 13:20
- StatusReceived → PublishedNVD modified 2026-10-19 08:51
- First seenunscoredNVD modified 2026-10-19 09:18
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://git.kernel.org/stable/c/4bf3328eeec9afc2a55632ff47fc18101ea62d73
- https://git.kernel.org/stable/c/5cec3e60e9f2d1324179df3aa91656f90095cf8f
- https://git.kernel.org/stable/c/a5fda7def04d98ab7c5cbb2394714fb1f8c56cb5
- https://git.kernel.org/stable/c/dde75313eed0b014c437f48dd75c0308b592cbf9
- https://git.kernel.org/stable/c/dea8f13c3dfad8b990f8ea96c997aabeebbc1d22