<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T15:20:35.036038+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-89717</id>
    <title>CVE-2026-89717 — zram: set default primary compressor in zram_destroy_comps()</title>
    <updated>2026-09-29T15:20:41.601073+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>zram: set default primary compressor in zram_destroy_comps()</p>
<p>Patch series "zram: fix zram issues reported by sashiko".</p>
<p>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.</p>
<p>This patch (of 2):</p>
<p>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()-&gt;strcmp() can be called on a NULL compressor.  Set
default primary compressor in zram_destroy_comps().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89717"/>
  </entry>
</feed>
