Unspecified impact via superblock read race
Published Oct 23, 2026 · Updated Oct 23, 2026
A race in Linux Btrfs zoned superblock handling allows local users to cause unspecified impact via concurrent block-size changes. In fs/btrfs/zoned.c, sb_write_pointer() calls read_cache_page_gfp() without the mapping invalidate lock, leaving the read unsynchronized with BLKBSZSET. Reachability requires the zoned superblock read path and a concurrent block-size change on the same device; the published fix does not establish a specific security consequence or minimum attacker privileges.
Summary
What happened
A race in Linux Btrfs zoned superblock handling allows local users to cause unspecified impact via concurrent block-size changes. In fs/btrfs/zoned.c, sb_write_pointer() calls read_cache_page_gfp() without the mapping invalidate lock, leaving the read unsynchronized with BLKBSZSET. Reachability requires the zoned superblock read path and a concurrent block-size change on the same device; the published fix does not establish a specific security consequence or minimum attacker privileges.
The record
- CVE
- CVE-2026-98907
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.15.222
- Affected versionversion=0 <6.1.189
- Affected versionversion=0 <6.12.111
- Affected versionversion=0 <6.18.53
- Affected versionversion=0 <6.6.158
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <123b9a545f4d0348e81f558a032bf2a93ee5722f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1a6c92aa7242a04e4349c0ea213dbf703a1c9891
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <80cd97c5e90096d040a623851795eac92fbd0ff1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a0dc28359a8a26f970ccd250b126a2e0bd4118a5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a58cab4535f085adc0f93d7efd7952ef437371da
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c9b38f2eab5a9bd74087390318d93ccdd8d2deff
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us