CVE-2026-53018 json
f2fs: avoid reading already updated pages during GC
published 2026-06-24 4 mo ago modified 2026-10-30 9 d ago also EUVD-2026-38886
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
f2fs: avoid reading already updated pages during GC
We found the following issue during fuzz testing:
page: refcount:3 mapcount:0 mapping:00000000b6e89c65 index:0x18b2dc pfn:0x161ba9 memcg:f8ffff800e269c00 aops:f2fs_meta_aops ino:2 flags: 0x52880000000080a9(locked|waiters|uptodate|lru|private|zone=1|kasantag=0x4a) raw: 52880000000080a9 fffffffec6e17588 fffffffec0ccc088 a7ffff8067063618 raw: 000000000018b2dc 0000000000000009 00000003ffffffff f8ffff800e269c00 page dumped because: VM_BUG_ON_FOLIO(folio_test_uptodate(folio)) page_owner tracks the page as allocated post_alloc_hook+0x58c/0x5ec prep_new_page+0x34/0x284 get_page_from_freelist+0x2dcc/0x2e8c __alloc_pages_noprof+0x280/0x76c __folio_alloc_noprof+0x18/0xac __filemap_get_folio+0x6bc/0xdc4 pagecache_get_page+0x3c/0x104 do_garbage_collect+0x5c78/0x77a4 f2fs_gc+0xd74/0x25f0 gc_thread_func+0xb28/0x2930 kthread+0x464/0x5d8 ret_from_fork+0x10/0x20 ------------[ cut here ]------------ kernel BUG at mm/filemap.c:1563! folio_end_read+0x140/0x168 f2fs_finish_read_bio+0x5c4/0xb80 f2fs_read_end_io+0x64c/0x708 bio_endio+0x85c/0x8c0 blk_update_request+0x690/0x127c scsi_end_request+0x9c/0xb8c scsi_io_completion+0xf0/0x250 scsi_finish_command+0x430/0x45c scsi_complete+0x178/0x6d4 blk_mq_complete_request+0xcc/0x104 scsi_done_internal+0x214/0x454 scsi_done+0x24/0x34
which is similar to the problem reported by syzbot: https://syzkaller.appspot.com/bug?extid=3686758660f980b402dc
This case is consistent with the description in commit 9bf1a3f ("f2fs: avoid GC causing encrypted file corrupted"): Page 1 is moved from blkaddr A to blkaddr B by move_data_block, and after being written it is marked as uptodate. Then, Page 1 is moved from blkaddr B to blkaddr C, VM_BUG_ON_FOLIO was triggered in the endio initiated by ra_data_block.
There is no need to read Page 1 again from blkaddr B, since it has already been updated. Therefore, avoid initiating I/O in this case.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.114, 6.18.33, 7.0.10, 7.1
- linux Debian 13 6.12.115-2
- linux Debian 14 7.0.10-1
debian advisories DEBIAN-CVE-2026-53018
- linux Ubuntu 26.04 LTS 7.0.0-28.28
- linux-aws Ubuntu 26.04 LTS 7.0.0-1009.9
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1008.8
- linux-gke Ubuntu 26.04 LTS 7.0.0-1003.4
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1010.10
- linux-azure Ubuntu 26.04 LTS 7.0.0-1010.10
- linux-raspi Ubuntu 26.04 LTS 7.0.0-1015.15
- linux-riscv Ubuntu 26.04 LTS 7.0.0-28.28.1
ubuntu advisories UBUNTU-CVE-2026-53018
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/ecf53b5c9ccba6e6a7db111722cc8bbfc92d4558 commit
- git.kernel.org/stable/c/c260c874a6d578a45105f98089b1f0db5c6ff0a3 commit
- git.kernel.org/stable/c/08423a9564d92e51505763b6b2f47b3da8b0a355 commit
- git.kernel.org/stable/c/4623c251496b99c530ce225c05334f4eac8b933a commit
- git.kernel.org/stable/c/b663ebb8a340eae5442e605b6acd2cff5677f016 commit
- git.kernel.org/stable/c/570e2ccc7cb35fe720106964e65060602d3d2ac4 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-53018 updated
kernel: f2fs: avoid reading already updated pages during GC
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/ecf53b5c9ccba6e6a7db111722cc8bbfc92d4558
- git.kernel.org /stable/c/c260c874a6d578a45105f98089b1f0db5c6ff0a3
- git.kernel.org /stable/c/08423a9564d92e51505763b6b2f47b3da8b0a355
-
git.kernel.org
/stable/c/4623c251496b99c530ce225c05334f4eac8b933a
patch
-
git.kernel.org
/stable/c/b663ebb8a340eae5442e605b6acd2cff5677f016
patch
-
git.kernel.org
/stable/c/570e2ccc7cb35fe720106964e65060602d3d2ac4
patch
Sources
- CVE List CVE-2026-53018
- NVD CVE-2026-53018
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.