Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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().

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 40 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 6e20720b12299595154857fa98222729f0d5823c – < a5fda7def04d98ab7c5cbb2394714fb1f8c56cb5
    • affected 486fd58af7ac1098b68370b1d4d9f94a2a1c7124 – < 4bf3328eeec9afc2a55632ff47fc18101ea62d73
    • affected 486fd58af7ac1098b68370b1d4d9f94a2a1c7124 – < 5cec3e60e9f2d1324179df3aa91656f90095cf8f
    • affected 486fd58af7ac1098b68370b1d4d9f94a2a1c7124 – < dea8f13c3dfad8b990f8ea96c997aabeebbc1d22
    • affected 486fd58af7ac1098b68370b1d4d9f94a2a1c7124 – < dde75313eed0b014c437f48dd75c0308b592cbf9
    • affected c4e5683c3031a33dc46954e99d37cbd2f706cdb6
    • affected 6.6.57 – < 6.6.160
    • affected 6.11.4 – < 6.12
  • Linux · Linux

    • affected 6.12
    • unaffected < 6.12
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89717 badge
[![CVE-2026-89717](https://cveledger.app/badge/CVE-2026-89717.svg)](https://cveledger.app/cve/CVE-2026-89717)

Record last updated .