CVE-2026-63817

CVE CVE-2026-63817EUVD EUVD-2026-45483Published 2026-07-19T12:02:16.000ZLast changed 2026-08-05T12:36:03.000ZCVSS 7.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: f2fs: validate compress cache inode only when enabled F2FS_COMPRESS_INO() uses NM_I(sbi)->max_nid as the synthetic inode number for the compressed page cache inode. That inode only exists when the compress_cache mount option is enabled. When compress_cache is disabled, max_nid is outside the valid inode range. A corrupted directory entry that points to ino == max_nid should therefore be rejected by f2fs_check_nid_range(). However, is_meta_ino() currently treats F2FS_COMPRESS_INO() as a meta inode unconditionally, so f2fs_iget() bypasses do_read_inode() and its nid range check, and instantiates a fake internal inode instead. Gate the compressed cache inode case on COMPRESS_CACHE, matching f2fs_init_compress_inode(). With compress_cache disabled, ino == max_nid now follows the normal inode path and is rejected as an out-of-range nid.

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.18.38; patch: 7.1.3; 6ce19aff0b8cd386860855185c6cd79337fc4d2b <0969926d987bbde9a1aa49da317582ba37095805; 6ce19aff0b8cd386860855185c6cd79337fc4d2b <77f216ff9ce5cde8eed9f6d12707e906dffdc9f7; patch: 5.15.212; 5.13.19 <5.14; patch: 0; 6ce19aff0b8cd386860855185c6cd79337fc4d2b <13e4b59d3a9413f66f116fa6c4828519b960a5ea; 6ce19aff0b8cd386860855185c6cd79337fc4d2b <fcc051d377a9701a452e7663a1a8223c26225df9; patch: 7.2-rc1; 6ce19aff0b8cd386860855185c6cd79337fc4d2b <29115b8c9172d34e67ab26cc4f6c209b7a236d7a; 6ce19aff0b8cd386860855185c6cd79337fc4d2b <16161444c30d8dff9428abbae42b72ce4e32a932; patch: 6.6.144; 6ce19aff0b8cd386860855185c6cd79337fc4d2b <5073c66a96a9c23c0c2533ed4ed06e42f9021208; 5.14; patch: 6.12.95; a23706426da9b611be5beae0f3faa260fb453b4e; patch: 6.1.177

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.