In the Linux kernel, the following vulnerability has been resolved: f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node() When __destroy_extent_node() sets the inode flag FI_NO_EXTEN…
Info
Summary
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node() When __destroy_extent_node() sets the inode flag FI_NO_EXTENT, it does not reset the length of the largest extent to 0 and update the inode folio. Since modifications to the extent tree are disallowed afterward, the cached largest extent may become stale. This can trigger the following error in xfstests generic/388: F2FS-fs (dm-0): sanity_check_extent_cache…
In-depth triage · Auto channel
No in-depth report has been generated yet (DR-003 v2 AI pipeline is under construction).
Sources
- NVD DATABASE
Original Links
- https://git.kernel.org/stable/c/1f70ddb28a3c71df124da5fa4040c808116d6bb9
- https://git.kernel.org/stable/c/20190e498057997532c7f186d081011f18e0a462
- https://git.kernel.org/stable/c/58a5deb220bcac4c73bf58954c0845644c997487
- https://git.kernel.org/stable/c/7e4d8f98be63f98856a5176b9188dada6e7ba9ee
- https://git.kernel.org/stable/c/edf12cbeeeabe799bd2ee21fdb5c336cce6fbad7
Timeline
- nvd_ingest NVD