Vulnerability · Published Jun 24, 2026 · Assigned by Linux

CVE-2026-53018f2fs: avoid reading already updated pages during GC

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 94.5% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-53018
Debian:13linux6.12.115-2DEBIAN-CVE-2026-53018
Debian:14linux7.0.10-1DEBIAN-CVE-2026-53018
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-53018
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux7.0.0-28.28UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-53018
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-aws7.0.0-1009.9UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-53018
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-azure7.0.0-1010.10UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-53018
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1009.9UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-53018
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-gcp7.0.0-1008.8UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-gke7.0.0-1003.4UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-ibm7.0.0-1010.10UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1016.16UBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2016.16UBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1009.9UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-53018
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-oracle7.0.0-1008.8UBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-53018
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-raspi7.0.0-1015.15UBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-53018
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-realtime7.0.0-28.28.1UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-53018
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-53018
Ubuntu:26.04:LTSlinux-riscv7.0.0-28.28.1UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-28.28.1~24.04.3UBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-53018
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-53018
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-53018

Affected products (as reported)

VendorProductVersions
Linux Linux 6aa58d8ad20a3323f42274c25820a6f54192422d – before ecf53b5c9ccba6e6a7db111722cc8bbfc92d45586aa58d8ad20a3323f42274c25820a6f54192422d – before c260c874a6d578a45105f98089b1f0db5c6ff0a36aa58d8ad20a3323f42274c25820a6f54192422d – before 08423a9564d92e51505763b6b2f47b3da8b0a3556aa58d8ad20a3323f42274c25820a6f54192422d – before 4623c251496b99c530ce225c05334f4eac8b933a6aa58d8ad20a3323f42274c25820a6f54192422d – before b663ebb8a340eae5442e605b6acd2cff5677f0166aa58d8ad20a3323f42274c25820a6f54192422d – before 570e2ccc7cb35fe720106964e65060602d3d2ac4
Linux Linux 4.19

References