CVE-2026-98269
btrfs: abort transaction on failure to update inode for hole punching and reflinking
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 2aaa66558172b017f36bf38ae69372813dedee9d, < 2605eb9ba3bbd4c9f455cfe6b85bd28a1da7067dUpgrade to: 2605eb9ba3bbd4c9f455cfe6b85bd28a1da7067dAffected: ≥ 2aaa66558172b017f36bf38ae69372813dedee9d, < 834a3b5c5f1ec0df48c1a6208f9989f4ffdaa0b6Upgrade to: 834a3b5c5f1ec0df48c1a6208f9989f4ffdaa0b6Affected: ≥ 2aaa66558172b017f36bf38ae69372813dedee9d, < 9588850bfa75c78ce73c2f6f72544d19d2e9beb6Upgrade to: 9588850bfa75c78ce73c2f6f72544d19d2e9beb6Affected: ≥ 2aaa66558172b017f36bf38ae69372813dedee9d, < 36c68dc909845c049e0286d229bc502947239452Upgrade to: 36c68dc909845c049e0286d229bc502947239452 + 1 more branchStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: btrfs: abort transaction on failure to update inode for hole punching and reflinking If we fail to update the inode we error out without aborting the transaction, which can result in a persistent inconsistency if after the failure the transaction is committed, as we have dropped file extent items from a range and either punched a hole or insert a new file extent item for that range (for reflinks). So add the missing transaction abort.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/2605eb9ba3bbd4c9f455cfe6b85bd28a1da7067d
- git.kernel.org/stable/c/834a3b5c5f1ec0df48c1a6208f9989f4ffdaa0b6
- git.kernel.org/stable/c/9588850bfa75c78ce73c2f6f72544d19d2e9beb6
And 2 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI