CVE-2026-98879 json
isofs: handle set_blocksize failures
published 19d ago modified 17d ago also EUVD-2026-108673
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
isofs: handle set_blocksize failures
isofs uses buffer_heads, which don't handle block size > PAGE_SIZE well. Without this, mounting we will hit the
BUG_ON(offset >= folio_size(folio));
in folio_set_bh on the first __bread_gfp call.
Patch / fix
- Linux Linux 7.2
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.6-1
debian advisories DEBIAN-CVE-2026-98879
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-98879
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.159.1-1
azure linux advisories AZL-110608
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/6db7f0ba365786304558db6a3d52013ae176e03e commit
- git.kernel.org/stable/c/61f277bf35f533b602984f0e55900111fe52f31a commit
- git.kernel.org/stable/c/cebde6d88e34396c29f2f001d90e921677cc17d6 commit
- git.kernel.org/stable/c/28d1f6aa14f5924e36602b7a31c9141d34de0b9c commit
- git.kernel.org/stable/c/9c97e3b1152d3092581745189f5d2f04c6404ef9 commit
- git.kernel.org/stable/c/9584ab6283721e5aab485c79bd06c2f78d89e55c commit
- git.kernel.org/stable/c/25ef4c4d9f0e96fb89c0ae0d7127c3f12a31bc32 commit
Is CVE-2026-98879 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98879 updated cvss 4.4
kernel: isofs: handle set_blocksize failures
-
Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/6db7f0ba365786304558db6a3d52013ae176e03e
- git.kernel.org /stable/c/61f277bf35f533b602984f0e55900111fe52f31a
- git.kernel.org /stable/c/cebde6d88e34396c29f2f001d90e921677cc17d6
- git.kernel.org /stable/c/28d1f6aa14f5924e36602b7a31c9141d34de0b9c
- git.kernel.org /stable/c/9c97e3b1152d3092581745189f5d2f04c6404ef9
- git.kernel.org /stable/c/9584ab6283721e5aab485c79bd06c2f78d89e55c
- git.kernel.org /stable/c/25ef4c4d9f0e96fb89c0ae0d7127c3f12a31bc32
Sources
- CVE List CVE-2026-98879
- NVD CVE-2026-98879
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.