CVE-2026-89830
Last modified
CVE-2026-89830 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix valid block count leak on data block allocation failure In __allocate_data_block(), when allocating a new data block (dn->data_blkaddr == NULL_ADDR), inc_valid_block_count() is called first to increment total_valid_block_count and i_blocks. If the subsequent f2fs_allocate_data_block() fails, the function returns the error directly without rolling back the already-incremented block counts, causing a permanent leak. Fix this by calling dec_valid_block_count() to undo the increment before returning the error. The condition old_blkaddr == NULL_ADDR precisely identifies the case where inc_valid_block_count() was called..
Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix valid block count leak on data block allocation failure In __allocate_data_block(), when allocating a new data block (dn->data_blkaddr == NULL_ADDR), inc_valid_block_count() is called first to increment total_valid_block_count and i_blocks. If the subsequent f2fs_allocate_data_block() fails, the function returns the error directly without rolling back the already-incremented block counts, causing a permanent leak. Fix this by calling dec_valid_block_count() to undo the increment before returning the error. The condition old_blkaddr == NULL_ADDR precisely identifies the case where inc_valid_block_count() was called.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 7d009e048d7cfcc21d400f2aba4c8bacbdebbd47, < 2d50b6d47e5671ff6a25834c5906d443356191f0; >= 7d009e048d7cfcc21d400f2aba4c8bacbdebbd47, < dde99df5a9d3b0ca6ac0a86f98799685f7399432; >= 7d009e048d7cfcc21d400f2aba4c8bacbdebbd47, < 931e1aa4d44c52ff8e0feb38420a8827c62e886b; >= 7d009e048d7cfcc21d400f2aba4c8bacbdebbd47, < 0f9af07ecc1ab486038373db6ae0436c5d674b19 |
| Linux | Linux | 6.9 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-89830?
How severe is CVE-2026-89830?
How do I fix CVE-2026-89830?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-89825In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89826In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-89827In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89828In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89829In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-8983Autel Maxi Charger Single firmware through V1.03.51 contains…9.8
- CVE-2026-89831In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89832In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89833In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89834In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89835In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89836In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-89830?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
