CVE-2026-99572: f2fs: fix to avoid potential reference count leak in do_garbage_collect()
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to avoid potential reference count leak in dogarbagecollect()
In dogarbagecollect(), we have reserved reference counts on summary cache of all segments, once gcthread encounter freezing, we need to release all reference counts.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.5-1 - Compensating control
In do_garbage_collect(), release all reserved reference counts when gc_thread encounters freezing.
Event History
Frequently Asked Questions
What condition triggers the reference-count leak?
The leak can occur when f2fs garbage collection has reserved reference counts on summary caches for segments and the garbage-collection thread encounters filesystem freezing before those references are released.
What is the immediate mitigation if an updated kernel cannot be deployed?
The provided information identifies the issue in the interaction between f2fs garbage collection and filesystem freezing, but does not provide a supported configuration workaround. Reducing or avoiding filesystem-freeze operations during f2fs garbage collection may avoid the stated trigger, but this is not documented as a complete mitigation.