CVE-2026-31702

published 1 May 2026 · updated 13 Nov 2026

f2fs: fix use-after-free of sbi in f2fs_compress_write_end_io()

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.6.136, Kernel 6.18.25, Kernel 7.0.2 and 8 more.

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix use-after-free of sbi in f2fs_compress_write_end_io() In f2fs_compress_write_end_io(), dec_page_count(sbi, type) can bring the F2FS_WB_CP_DATA counter to zero, unblocking f2fs_wait_on_all_pages() in f2fs_put_super() on a concurrent unmount CPU. The unmount path then proceeds to call f2fs_destroy_page_array_cache(sbi), which destroys sbi->page_array_slab via kmem_cache_destroy(), and eventually kfree(sbi). Meanwhile, the bio completion callback is still executing: when it reaches page_array_free(sbi, ...), it dereferences sbi->page_array_slab — a destroyed slab cache — to call kmem_cache_free(), causing a use-after-free. This is the same class of bug as CVE-2026-23234 (which fixed the equivalent race in f2fs_write_end_io() in data.c), but in the compressed writeback completion path that was not covered by that fix. Fix this by moving dec_page_count() to after page_array_free(), so that all sbi accesses complete before the counter decrement that can unblock unmount. For non-last folios (where atomic_dec_return on cic->pending_pages is nonzero), dec_page_count is called immediately before returning — page_array_free is not reached on this path, so there is no post-decrement sbi access. For the last folio, page_array_free runs while the F2FS_WB_CP_DATA counter is still nonzero (this folio has not yet decremented it), keeping sbi alive, and dec_page_count runs as the final operation.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=5.6 <6.6.136, >=6.13 <6.18.25, >=6.19 <7.0.2, >=6.7 <6.12.84, =7.1, >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <39d4ee19c1e7d753dd655aebee632271b171f43a, >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <57bc678f36ac03281e877c6b84877b43f964143f, >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <c76cf339b87975ae5b2c06d2d774d5667d25a12a, >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <ef57cd3329b40c739b9a2e1a8a21ecc4171c6280, >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <f5154cf3ce1c8193f0c1891d3769f62740cfe6fe, =5.6, >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <2c97dcb6147c8f7f25c629b93be1e69617de5d4a6.6.136, 6.18.25, 7.0.2, 6.12.84, 39d4ee19c1e7d753dd655aebee632271b171f43a, 57bc678f36ac03281e877c6b84877b43f964143f, c76cf339b87975ae5b2c06d2d774d5667d25a12a, ef57cd3329b40c739b9a2e1a8a21ecc4171c6280, f5154cf3ce1c8193f0c1891d3769f62740cfe6fe, 2c97dcb6147c8f7f25c629b93be1e69617de5d4a
linux-kernel: Kernel>=5.6.0 <6.1.175, >=6.13.0 <6.18.25, >=6.19.0 <7.0.2, >=6.2.0 <6.6.136, >=6.7.0 <6.12.846.1.175, 6.18.25, 7.0.2, 6.6.136, 6.12.84

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-31702 severity on Zeptric[![CVE-2026-31702](https://zeptric.io/badge/cve/CVE-2026-31702.svg)](https://zeptric.io/cve/CVE-2026-31702)