cve.bz

CVE-2026-90264 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: btrfs: always wait for ordered extents to avoid OE races [BUG] Syzbot reported a bug that there can be conflicting OEs for the same range: BTRFS critical (device loop4): panic in insert_ordered_extent:264: overlapping ordered extents, existing oe file_offset 16384 num_bytes 430080 flags 0x1089, new oe file_offset 16384 num_bytes 430080 flags 0x80 (errno=-17 Object alrea[ 179.162726][ T6897] BTRFS critical (device loop4): panic in insert_ordered_extent:264: overlapping ordered extents, existing oe file_offset 16384 num_bytes 430080 flags 0x1089, new oe file_offset 16384 num_bytes 430080 flags 0x80 (errno=-17 Object already exists) ------------[ cut here ]------------ kernel BUG at fs/btrfs/ordered-data.c:264! Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026 RIP: 0010:btrfs_alloc_ordered_extent+0x943/0xad0 Call Trace: <TASK> cow_file_range+0x744/0x12a0 fallback_to_cow+0x5ea/0xa00 run_delalloc_nocow+0x110c/0x17a0 btrfs_run_delalloc_range+0xbe4/0x1c20 writepage_delalloc+0x104d/0x1ba0 btrfs_writepages+0x1667/0x28b0 do_writepages+0x338/0x560 filemap_fdatawrite_range+0x1f2/0x300 btrfs_fdatawrite_range+0x54/0xf0 btrfs_direct_write+0x6a0/0xc30 btrfs_do_write_iter+0x329/0x790 do_iter_readv_writev+0x624/0x8d0 vfs_writev+0x34c/0x990 __se_sys_pwritev2+0x17a/0x2a0 do_syscall_64+0x174/0x580 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK> ---[ end trace 0000000000000000 ]--- [CAUSE] Since commit ff66fe666233 ("btrfs: fix incorrect buffered IO fallback for append direct writes"), if the direct IO finished short, we will revert the isize back to the original one, so that append writes can be respected during the buffered fallback. Normally we rely on lock_and_cleanup_extent_if_need() function during buffered writeback to wait for any existing ordered extents. But that ordered extent waiting only happens if the start_pos is inside the isize. Since we have reverted the isize during failed direct IO, we will not wait for any ordered extents. This means we can have a race where the direct IO OE is still in the tree, finished but not yet removed, then we're inserting the OE for the buffered write, causing the above crash. [FIX] Make the OE wait to be unconditional, to handle the reverted isize situation. And since lock_and_cleanup_extent_if_need() now either lock the extents or return -EAGAIN, also remove the branches that handles no-extent-locked cases, and rename it to remove the "_if_need" suffix. The following micro benchmark shows the runtime difference for btrfs_buffered_write(), doing `xfs_io -f -c "pwrite 0 1m"` workload, all values are the average runtime in nano seconds. function runtime | before | after -----------------------------------+-------------+--------------- lock_and_cleanup_extent_if_need() | 58.2 | 183.0 btrfs_buffered_write() | 2115.6 | 2973.3 The overall runtime of btrfs_buffered_write() is still pretty tiny (still less than 3 micro seconds), I'd say the extra cost is still acceptable. An alternative to fix this problem is to wait ordered extents during iomap_end() where the isize revert is done. But that solution will break nowait requirement, as if a nowait direct IO finished short, we have to wait for the OEs unconditionally or the next append buffered IO can still hit the same problem. So here we have to move the wait cost to buffered write, but at least the code is slightly more streamline.
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.1.191
  • Linux Linux: fixed in 6.6.160
  • Linux Linux: fixed in 6.12.114
  • Linux Linux: fixed in 6.18.52
  • Linux Linux: fixed in 7.2.6
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, openSUSE, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-90264 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-90264?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-90264?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-90264 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 6.1.178 before 6.1.191
Linuxfrom 6.6.145 before 6.6.160
Linuxfrom 6.12.97 before 6.12.114
Linuxfrom 6.18.40 before 6.18.52
Linuxfrom 5.15.212 before 5.16
Linuxfrom 7.1.4 before 7.2
Linux7.2 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.191
Linux6.66.6.160
Linux6.126.12.114
Linux6.186.18.52
Linux7.27.2.6
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-90264
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-90264
Debian13linux6.12.115-2DEBIAN-CVE-2026-90264
Debian14linux7.2.6-1DEBIAN-CVE-2026-90264
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-90264
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-90264
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-90264
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 46 moreno fix listedUBUNTU-CVE-2026-90264
Ubuntu24.04:LTSlinux, linux-aws, linux-riscv and 29 moreno fix listedUBUNTU-CVE-2026-90264
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-90264 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-90264 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-90264 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-90264 USN-8959-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-90264 USN-9020-1
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-90264
Ubuntu26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-90264 USN-8959-1
16 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.2.7-1.1openSUSE-SU-2026:11880-1
Azure Linux3kernelno fix listedAZL-102291
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-90264
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-90264
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-90264

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

Red Hat rates this Moderate.

Red Hat's statement

A MODERATE severity race condition flaw was found in the Linux kernel's btrfs filesystem. When a direct I/O append write finishes short, the kernel reverts the file size before falling back to a buffered write, and under this condition the buffered write path may skip waiting for a still-outstanding direct I/O ordered extent. This allows two ordered extents to be inserted for the same file range, triggering a kernel BUG and panic. A local attacker able to perform file writes on a mounted btrfs filesystem could exploit this race to crash the system, resulting in a denial of service. The vulnerable code, introduced by a recent upstream btrfs direct I/O change, is not present in the Linux kernel versions shipped in Red Hat Enterprise Linux 7, 8, 9, and 10 (including kernel-rt), Red Hat In-Vehicle OS, or the RHEL CoreOS images used by OpenShift Container Platform, so those products are not affected. The Red Hat Enterprise Linux 6 ELS kernel is recorded as out of support scope for this issue.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not 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-90264.

References

Check your stackJSON