CVE-2026-98269

Unknown

Last modified

CVE-2026-98269 is a vulnerability of currently unknown severity. 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..

Description

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 2aaa66558172b017f36bf38ae69372813dedee9d, < 2605eb9ba3bbd4c9f455cfe6b85bd28a1da7067d; >= 2aaa66558172b017f36bf38ae69372813dedee9d, < 834a3b5c5f1ec0df48c1a6208f9989f4ffdaa0b6; >= 2aaa66558172b017f36bf38ae69372813dedee9d, < 9588850bfa75c78ce73c2f6f72544d19d2e9beb6; >= 2aaa66558172b017f36bf38ae69372813dedee9d, < 36c68dc909845c049e0286d229bc502947239452; >= 2aaa66558172b017f36bf38ae69372813dedee9d, < 97fcd34aa9fd73cefe3120ac9a82ca9d7763922f
LinuxLinux3.7

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98269?
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.
How severe is CVE-2026-98269?
Severity scoring for CVE-2026-98269 is pending analysis.
How do I fix CVE-2026-98269?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-98269?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST