CVE-2026-31702

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

State
Published
Severity
Not scored
Published
May 1, 2026
Updated
Jun 14, 2026
Reserved
Mar 9, 2026

Read the record on cve.org

Description

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 4c8ff7095bef64fc47e996a938f7d57f9e077da3 to before 57bc678f36ac03281e877c6b84877b43f964143fAffected
  • 4c8ff7095bef64fc47e996a938f7d57f9e077da3 to before ef57cd3329b40c739b9a2e1a8a21ecc4171c6280Affected
  • 4c8ff7095bef64fc47e996a938f7d57f9e077da3 to before f5154cf3ce1c8193f0c1891d3769f62740cfe6feAffected
  • 4c8ff7095bef64fc47e996a938f7d57f9e077da3 to before c76cf339b87975ae5b2c06d2d774d5667d25a12aAffected
  • 4c8ff7095bef64fc47e996a938f7d57f9e077da3 to before 2c97dcb6147c8f7f25c629b93be1e69617de5d4aAffected
  • 4c8ff7095bef64fc47e996a938f7d57f9e077da3 to before 39d4ee19c1e7d753dd655aebee632271b171f43aAffected
LinuxLinux
  • 5.6Affected
  • before 5.6Not affected
  • 6.1.175 through 6.1.*Not affected
  • 6.6.136 through 6.6.*Not affected
  • 6.12.84 through 6.12.*Not affected
  • 6.18.25 through 6.18.*Not affected
  • 7.0.2 through 7.0.*Not affected
  • 7.1 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.