CVE-2026-89717: zram: set default primary compressor in zram_destroy_comps()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 4bf3328eeec9afc2a55632ff47fc18101ea62d73, 5cec3e60e9f2d1324179df3aa91656f90095cf8f, 6.12.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 4bf3328eeec9afc2a55632ff47fc18101ea62d73, 5cec3e60e9f2d1324179df3aa91656f90095cf8f, 6.12 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Sep 11, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- c4e5683c3031a33dc46954e99d37cbd2f706cdb6, 6.12affected
- 6e20720b12299595154857fa98222729f0d5823c and later · before a5fda7def04d98ab7c5cbb2394714fb1f8c56cb5affected · git
- 486fd58af7ac1098b68370b1d4d9f94a2a1c7124 and later · before 4bf3328eeec9afc2a55632ff47fc18101ea62d73affected · git
- 486fd58af7ac1098b68370b1d4d9f94a2a1c7124 and later · before 5cec3e60e9f2d1324179df3aa91656f90095cf8faffected · git
- 486fd58af7ac1098b68370b1d4d9f94a2a1c7124 and later · before dea8f13c3dfad8b990f8ea96c997aabeebbc1d22affected · git
- 486fd58af7ac1098b68370b1d4d9f94a2a1c7124 and later · before dde75313eed0b014c437f48dd75c0308b592cbf9affected · git
- 6.6.57 and later · before 6.6.160affected · semver
- 6.11.4 and later · before 6.12affected · semver
- before 6.12not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89715Sep 11, 2026 · NFS/localio: fix ref leak on nfs_uuid_add_file failure0Monitor
- ← EarlierCVE-2026-89716Sep 11, 2026 · zram: validate deflate params0Monitor
- Later →CVE-2026-89718Sep 11, 2026 · zram: fix out-of-bounds access in writeback_store()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4bf3328eeec9afc2a55632ff47fc18101ea62d73 | Vendor (CNA) |
| Linux Linux | 5cec3e60e9f2d1324179df3aa91656f90095cf8f | Vendor (CNA) |
| Linux Linux | 6.12 | Vendor (CNA) |
| Linux Linux | 6.6.160 | Vendor (CNA) |
| Linux Linux | a5fda7def04d98ab7c5cbb2394714fb1f8c56cb5 | Vendor (CNA) |
| Linux Linux | dde75313eed0b014c437f48dd75c0308b592cbf9 | Vendor (CNA) |
| Linux Linux | dea8f13c3dfad8b990f8ea96c997aabeebbc1d22 | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.