f2fs: validate compress cache inode only when enabled
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.15.212, 6.1.177, 6.12.95, 6.18.38, 6.6.144, 7.1.3
- CVEs
- CVE-2026-63817
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 28 Oct 2026, 08:57 UTC · Revision 1
Source evidence
f2fs: validate compress cache inode only when enabled
core-osv · Original sourcePublished 19 Jul 2026, 12:02 UTC
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.
osv:CVE-2026-63817
Kernel
Fixed versions: 5.15.212, 6.1.177, 6.6.144, 6.12.95, 6.18.38, 7.1.3
Complete source record
{
"id": "e3e13e885de8797d00c1ea8d52085fb3687d51522a71a037b32b61b27e585ca2",
"url": "https://osv.dev/vulnerability/CVE-2026-63817",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "f2fs: validate compress cache inode only when enabled",
"summary": "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.",
"evidence": "osv:CVE-2026-63817",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.15.212",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.177",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.144",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.95",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.38",
"evidence": "/affected/1/ranges"
},
{
"value": "7.1.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-63817",
"aliases": [
"CVE-2026-63817"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6ce19aff0b8cd386860855185c6cd79337fc4d2b"
},
{
"fixed": "fcc051d377a9701a452e7663a1a8223c26225df9"
},
{
"fixed": "29115b8c9172d34e67ab26cc4f6c209b7a236d7a"
},
{
"fixed": "13e4b59d3a9413f66f116fa6c4828519b960a5ea"
},
{
"fixed": "16161444c30d8dff9428abbae42b72ce4e32a932"
},
{
"fixed": "77f216ff9ce5cde8eed9f6d12707e906dffdc9f7"
},
{
"fixed": "0969926d987bbde9a1aa49da317582ba37095805"
},
{
"fixed": "5073c66a96a9c23c0c2533ed4ed06e42f9021208"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "5.13.19"
},
{
"fixed": "5.14"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "a23706426da9b611be5beae0f3faa260fb453b4e"
}
]
}
],
"versions": [
"v5.13.19"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-63817.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.14.0"
},
{
"fixed": "5.15.212"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.177"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.144"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.95"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.38"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-63817.json"
}
}
],
"modified": "2026-10-08T02:51:28.839184386Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0969926d987bbde9a1aa49da317582ba37095805",
"https://git.kernel.org/stable/c/13e4b59d3a9413f66f116fa6c4828519b960a5ea",
"https://git.kernel.org/stable/c/16161444c30d8dff9428abbae42b72ce4e32a932",
"https://git.kernel.org/stable/c/29115b8c9172d34e67ab26cc4f6c209b7a236d7a",
"https://git.kernel.org/stable/c/5073c66a96a9c23c0c2533ed4ed06e42f9021208",
"https://git.kernel.org/stable/c/77f216ff9ce5cde8eed9f6d12707e906dffdc9f7",
"https://git.kernel.org/stable/c/fcc051d377a9701a452e7663a1a8223c26225df9",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/63xxx/CVE-2026-63817.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-63817",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/63xxx/CVE-2026-63817.json"
}
},
"related_cves": [
{
"value": "CVE-2026-63817",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 98311,
"published_at": "2026-07-19T12:02:16.441+00:00"
}