CVE-2026-98907: Linux kernel · btrfs: protect sb_write_pointer() with invalidate lock
Source GCVE Database
Not known to be exploited : upgrade to 123b9a545f4d0348e81f558a032bf2a93ee5722f or 80cd97c5e90096d040a623851795eac92fbd0ff1 when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 123b9a545f4d0348e81f558a032bf2a93ee5722f, 80cd97c5e90096d040a623851795eac92fbd0ff1
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to 123b9a545f4d0348e81f558a032bf2a93ee5722f or 80cd97c5e90096d040a623851795eac92fbd0ff1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to address this vulnerability by adding the mapping invalidate lock around the read operation in sb_write_pointer(). Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the input data; therefore, check the vendor advisory for current remediation guidance.
Description
A vulnerability in the Linux kernel's Btrfs filesystem was resolved by adding a lock to protect the sb_write_pointer() function. This function reads the super block from the block device page cache, and previously had a race condition related to block size changes. The fix involves taking the mapping invalidate lock around the read operation to serialize it against block size changes.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98907 (opens in a new tab)
- git.kernel.org/stable/c/123b9a545f4d0348e81f558a032bf2a93ee5722f (opens in a new tab)
- git.kernel.org/stable/c/1a6c92aa7242a04e4349c0ea213dbf703a1c9891 (opens in a new tab)
- git.kernel.org/stable/c/80cd97c5e90096d040a623851795eac92fbd0ff1 (opens in a new tab)
- git.kernel.org/stable/c/a0dc28359a8a26f970ccd250b126a2e0bd4118a5 (opens in a new tab)
- git.kernel.org/stable/c/a58cab4535f085adc0f93d7efd7952ef437371da (opens in a new tab)
- git.kernel.org/stable/c/c9b38f2eab5a9bd74087390318d93ccdd8d2deff (opens in a new tab)