CVE-2026-63812

Last refreshed2026-10-30

Status: UPDATED | Advisory ID: CVE-2026-63812

Key Details

CVE	CVE-2026-63812
CVSS Score / Version	7.8 (High) / CVSS v3.1
Updated	2026-10-30
CVSS Vector	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`
CVSS Prose	attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products	Linux Kernel

Vendor	Product	Affected Versions	Patch Status
Linux	Linux Kernel

Vendor

Product

Affected Versions

Patch Status

Linux

Linux Kernel

Subsystems	OT Supporting Infrastructure
Sectors	All Sectors

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. (NVD)

Monitor Linux's web page for any future patch releases.

Source	Reference
NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-63812
CVE	https://www.cve.org/CVERecord?id=CVE-2026-63812

Source

Reference

NVD

CVE