CVE-2026-63816
CVE CVE-2026-63816EUVD EUVD-2026-45482Published 2026-07-19T12:02:15.000ZLast changed 2026-08-05T12:36:02.000ZCVSS 7.8
What the advisory describes
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.
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 3db1de0e582c358dd013f3703cd55b5fe4076436 <56038756aae68312df00d4aa1d97e51ef3aca725; 3db1de0e582c358dd013f3703cd55b5fe4076436 <e0288584baa5dc41df4a829a023c4c1b33fe53d7; 5.18.18 <5.19; patch: 7.2-rc1; patch: 6.6.145; 3db1de0e582c358dd013f3703cd55b5fe4076436 <7d3ae21783e5914c1761ac7d63f882d3d70800e9; patch: 6.12.96; 3db1de0e582c358dd013f3703cd55b5fe4076436 <a805fec35c201c59643ddcde713bce4051c8ee27; patch: 6.18.39; 5.19; 6db52f1944417c2601182a591a704e2f119c5215; 3db1de0e582c358dd013f3703cd55b5fe4076436 <a499f77c06050a28c897bdbd86cd2f0721ae0743; patch: 7.1.3; patch: 0
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 daysPatchlage 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.