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-63816f2fs: atomic: fix UAF issue on f2fs_inode_info.atomic_inode

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: atomic: fix UAF issue on f2fs_inode_info.atomic_inode - ioctl(F2FS_IOC_GARBAGE_COLLECT_RANGE) - shrink - f2fs_gc - gc_data_segment - ra_data_block(cow_inode) - mapping = F2FS_I(inode)->atomic_inode->i_mapping : f2fs_is_cow_file(cow_inode) is true - f2fs_evict_inode(atomic_inode) - clear_inode_flag(fi->cow_inode, FI_COW_FILE) - F2FS_I(fi->cow_inode)->atomic_inode = NULL ... - truncate_inode_pages_final(atomic_inode) - f2fs_grab_cache_folio(mapping) : create folio in atomic_inode->mapping - clear_inode(atomic_inode) - BUG_ON(atomic_inode->i_data.nrpages) We need to add a reference on fi->atomic_inode before using its mapping field during garbage collection, otherwise, it will cause UAF issue.

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-63816, 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 98% 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 3db1de0e582c358dd013f3703cd55b5fe4076436 – < 7d3ae21783e5914c1761ac7d63f882d3d70800e9
    • affected 3db1de0e582c358dd013f3703cd55b5fe4076436 – < 56038756aae68312df00d4aa1d97e51ef3aca725
    • affected 3db1de0e582c358dd013f3703cd55b5fe4076436 – < a499f77c06050a28c897bdbd86cd2f0721ae0743
    • affected 3db1de0e582c358dd013f3703cd55b5fe4076436 – < a805fec35c201c59643ddcde713bce4051c8ee27
    • affected 3db1de0e582c358dd013f3703cd55b5fe4076436 – < e0288584baa5dc41df4a829a023c4c1b33fe53d7
    • affected 6db52f1944417c2601182a591a704e2f119c5215
    • affected 5.18.18 – < 5.19
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.3 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .