Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-63817f2fs: validate compress cache inode only when enabled

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 29 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63817, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 6ce19aff0b8cd386860855185c6cd79337fc4d2b – < fcc051d377a9701a452e7663a1a8223c26225df9
    • affected 6ce19aff0b8cd386860855185c6cd79337fc4d2b – < 29115b8c9172d34e67ab26cc4f6c209b7a236d7a
    • affected 6ce19aff0b8cd386860855185c6cd79337fc4d2b – < 13e4b59d3a9413f66f116fa6c4828519b960a5ea
    • affected 6ce19aff0b8cd386860855185c6cd79337fc4d2b – < 16161444c30d8dff9428abbae42b72ce4e32a932
    • affected 6ce19aff0b8cd386860855185c6cd79337fc4d2b – < 77f216ff9ce5cde8eed9f6d12707e906dffdc9f7
    • affected 6ce19aff0b8cd386860855185c6cd79337fc4d2b – < 0969926d987bbde9a1aa49da317582ba37095805
    • affected 6ce19aff0b8cd386860855185c6cd79337fc4d2b – < 5073c66a96a9c23c0c2533ed4ed06e42f9021208
    • affected a23706426da9b611be5beae0f3faa260fb453b4e
    • affected 5.13.19 – < 5.14
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.177 – ≤ 6.1.*
    • unaffected 6.6.144 – ≤ 6.6.*
    • unaffected 6.12.95 – ≤ 6.12.*
    • unaffected 6.18.38 – ≤ 6.18.*
    • unaffected 7.1.3 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63817 badge
[![CVE-2026-63817](https://cveledger.app/badge/CVE-2026-63817.svg)](https://cveledger.app/cve/CVE-2026-63817)

Record last updated .