CVSS 3.1
5.5 mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HMedium (5.5) in linux linux kernel. EPSS 0.1% 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:N/A:HExplain CVE-2026-98090 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98090?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98090?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-98090 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 | from 5.15.11 before 5.15.222 |
| Linux | 5.16 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 5.15 | 5.15.222 |
| Linux | 6.1 | 6.1.189 |
| Linux | 6.6 | 6.6.158 |
| Linux | 6.12 | 6.12.111 |
| Linux | 6.18 | 6.18.53 |
| Linux | 7.2 | 7.2.7 |
| Linux | later releases | 7.3 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.190-1 | DEBIAN-CVE-2026-98090 |
| Debian | 12 | linux-6.12 | 6.12.111-1~deb12u1 | DEBIAN-CVE-2026-98090 |
| Debian | 13 | linux | 6.12.111-1 | DEBIAN-CVE-2026-98090 |
| Debian | 14 | linux | 7.2.7-1 | DEBIAN-CVE-2026-98090 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-98090 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-98090 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-98090 |
| Ubuntu | 22.04:LTS | linux | 5.15.0-202.212 | UBUNTU-CVE-2026-98090 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-aws | 5.15.0-1119.126 | UBUNTU-CVE-2026-98090 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-98090 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure | 5.15.0-1125.134 | UBUNTU-CVE-2026-98090 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-98090 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde | 5.15.0-1124.133 | UBUNTU-CVE-2026-98090 USN-8962-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-98090 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp | 5.15.0-1120.130 | UBUNTU-CVE-2026-98090 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-98090 USN-9024-1 |
| 78 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| openSUSE | Tumbleweed | kernel-source | 7.2.9-1.1 | openSUSE-SU-2026:12074-1 |
| Azure Linux | 3 | kernel | 6.6.158.1-1 | AZL-104367 |
| Alpaquita | 23 | linux-lts | 6.1.189-r0 | BELL-CVE-2026-98090 |
| Alpaquita | 25 | linux-lts | 6.12.111-r0 | BELL-CVE-2026-98090 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-CVE-2026-98090 |
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; Microsoft's Azure Linux vulnerability data, MIT; 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.
A use-after-free condition can occur after a failed Btrfs sprout operation because latest_dev and possibly s_bdev may continue to reference the new device after that device has been removed and released. A later call to btrfs_show_devname() can dereference the stale device pointer and cause a kernel crash. For the CVSS the PR:L value is used for the paranoid score because a reduced-capability service account or container root may have delegated access to Btrfs administration and the relevant block device without having unrestricted host root access. The attack is local and requires a failed sprout setup followed by access to the path that obtains the active device name. It is not directly network reachable. Impact is at least a local denial of service via kernel crash. Reuse of the freed allocation may permit limited confidentiality or integrity impact in a worst case interpretation, but the visible path does not establish an arbitrary write 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-98090.