CVE-2026-63812

CVE CVE-2026-63812EUVD EUVD-2026-45478Published 2026-07-19T12:02:13.000ZLast changed 2026-08-05T12:35:58.000ZCVSS 7.8

What the advisory describes

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: inode (ino=1761) extent info [220057, 57, 6] is incorrect, run fsck to fix In the f2fs_drop_inode path, __destroy_extent_node() does not need to guarantee that et->node_cnt is 0, because concurrency with writeback is expected in this path, and writeback may update the extent cache. This patch reverts commit ed78aeebef05 ("f2fs: fix node_cnt race between extent node destroy and writeback"), and remove the unnecessary zero check of et->node_cnt.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 6.6.144; patch: 7.1.3; ed78aeebef05212ef7dca93bd931e4eff67c113f <1f70ddb28a3c71df124da5fa4040c808116d6bb9; 6.18.30 <6.18.38; 6.6.140 <6.6.144; 42dd1c91f993431d0b399502479d00e6ad1bca71 <7e4d8f98be63f98856a5176b9188dada6e7ba9ee; b0e4395870eb3441ddc959f6710b5f6ca61aff26 <20190e498057997532c7f186d081011f18e0a462; 7.0.7 <7.1; 0559a0e962aacbb47519e26ee663be04b72dcb92; patch: 0; 6.12.88 <6.12.95; patch: 7.2-rc1; patch: 6.18.38; ed78aeebef05212ef7dca93bd931e4eff67c113f <edf12cbeeeabe799bd2ee21fdb5c336cce6fbad7; patch: 6.12.95; ab1eaf9d5c99042f5b0243bf67a06283a4c0757f <58a5deb220bcac4c73bf58954c0845644c997487; 7.1

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.