CVSS 3.1
7.1 highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HHigh (7.1) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HExplain CVE-2026-90260 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-90260?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-90260?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-90260 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 6.8 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.12 | 6.12.114 |
| Linux | 6.18 | 6.18.52 |
| Linux | 7.2 | 7.2.6 |
| Linux | later releases | 7.3 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux-6.12 | 6.12.115-2~deb12u1 | DEBIAN-CVE-2026-90260 |
| Debian | 13 | linux | 6.12.115-2 | DEBIAN-CVE-2026-90260 |
| Debian | 14 | linux | 7.2.6-1 | DEBIAN-CVE-2026-90260 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-90260 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-90260 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-90260 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 more | no fix listed | UBUNTU-CVE-2026-90260 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 43 more | no fix listed | UBUNTU-CVE-2026-90260 |
| Ubuntu | 24.04:LTS | linux-aws-7.0 | 7.0.0-1017.18~24.04.1 | UBUNTU-CVE-2026-90260 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1019.19~24.04.1 | UBUNTU-CVE-2026-90260 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-gcp-7.0 | 7.0.0-1017.19~24.04.1 | UBUNTU-CVE-2026-90260 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-42.42~24.04.1 | UBUNTU-CVE-2026-90260 USN-8959-1 |
| Ubuntu | 24.04:LTS | linux-nvidia-tegra | 6.8.0-1039.40 | UBUNTU-CVE-2026-90260 USN-9091-1 |
| Ubuntu | 24.04:LTS | linux-oracle-7.0 | 7.0.0-1016.18~24.04.1 | UBUNTU-CVE-2026-90260 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-42.42.1~24.04.1 | UBUNTU-CVE-2026-90260 |
| 16 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| openSUSE | Tumbleweed | kernel-source | 7.2.7-1.1 | openSUSE-SU-2026:11880-1 |
| Alpaquita | 25 | linux-lts | 6.12.115-r0 | BELL-CVE-2026-90260 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-CVE-2026-90260 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.
Red Hat rates this Moderate.
On a zoned Btrfs filesystem, a freed but still dirty tree block can be scheduled for a zero write only to advance the zone write pointer. The old path zeroed the folios owned by the live extent buffer, even though later code could still read its header. A later call to btrfs_free_tree_block can therefore observe a zero bytenr, create an invalid delayed reference, corrupt the extent tree, trigger an assertion or abort the filesystem. For the CVSS the PR:L reflects that an unprivileged local user with write access to an already mounted affected filesystem may be able to generate the required filesystem workload. Creating and mounting the zoned Btrfs filesystem still normally requires administrative setup. The issue is not directly network reachable. The demonstrated impact includes filesystem metadata corruption and denial of service. Limited confidentiality impact is retained only in the paranoid score because corrupted extent metadata could theoretically cause incorrect data references, but the supplied code does not establish a reliable disclosure primitive.
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Out of support scope | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Not affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Not affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-90260.