Skip to main content
VulnerabilityPublished Updated

CVE-2026-63819: Linux kernel · f2fs: fix to do sanity check on f2fs_get_node_folio_ra()

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.8 High.

Data as of 18 Nov 2026, 22:48 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Linux)CVSS 3.17.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel by adding sanity checks to detect inconsistent node chains in the f2fs filesystem. Users should apply the official Linux kernel updates that include this fix once available. Until patched, avoid using untrusted or corrupted f2fs filesystems that could trigger this issue.

Description

CVE-2026-63819 is a high-severity vulnerability in the Linux kernel's f2fs filesystem implementation. It involves a missing sanity check in the function f2fs_get_node_folio_ra(), which can lead to a kernel BUG and system panic due to invalid inode node data. The flaw arises from corrupted inode data causing inconsistent node chains, triggering a kernel crash during file truncation operations.

References

Community reviews

Loading reviews…