CVE-2026-53018

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated Jul 15, 2026
No patch confirmed yet.
generic

f2fs: avoid reading already updated pages during GC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b663ebb8a340eae5442e605b6acd2cff5677f016
generic

f2fs: avoid reading already updated pages during GC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/570e2ccc7cb35fe720106964e65060602d3d2ac4
generic

f2fs: avoid reading already updated pages during GC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4623c251496b99c530ce225c05334f4eac8b933a

Vendor Advisories for CVE-2026-53018(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 63× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 164 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 20:08 UTCEG score recompute
  11. 2026-08-30 20:08 UTCVendor advisory
  12. 2026-08-30 20:08 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-28 04:44 UTCEG score recompute
  17. 2026-08-28 04:44 UTCVendor advisory
  18. 2026-08-28 04:44 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 14:32 UTCEG score recompute
  23. 2026-08-24 14:32 UTCVendor advisory
  24. 2026-08-24 14:32 UTCGHSA enrichment
  25. 2026-08-23 13:42 UTCEG score recompute
Show 75 more
  1. 2026-08-23 13:42 UTCVendor advisory
  2. 2026-08-23 13:42 UTCGHSA enrichment
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-22 13:04 UTCEG score recompute
  5. 2026-08-22 13:04 UTCVendor advisory
  6. 2026-08-22 13:04 UTCGHSA enrichment
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 08:07 UTCEG score recompute
  9. 2026-08-21 08:07 UTCVendor advisory
  10. 2026-08-21 08:07 UTCGHSA enrichment
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-20 07:27 UTCEG score recompute
  13. 2026-08-20 07:27 UTCVendor advisory
  14. 2026-08-20 07:27 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-19 02:09 UTCEG score recompute
  17. 2026-08-19 02:09 UTCVendor advisory
  18. 2026-08-19 02:09 UTCGHSA enrichment
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 00:29 UTCEG score recompute
  22. 2026-08-17 00:29 UTCVendor advisory
  23. 2026-08-17 00:29 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 02:14 UTCEPSS rescore
  26. 2026-08-15 23:50 UTCEG score recompute
  27. 2026-08-15 23:50 UTCVendor advisory
  28. 2026-08-15 23:50 UTCGHSA enrichment
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 23:11 UTCVendor advisory
  31. 2026-08-14 23:11 UTCGHSA enrichment
  32. 2026-08-13 22:32 UTCEG score recompute
  33. 2026-08-13 22:32 UTCVendor advisory
  34. 2026-08-13 22:32 UTCGHSA enrichment
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-12 21:53 UTCEG score recompute
  37. 2026-08-12 21:53 UTCVendor advisory
  38. 2026-08-12 21:53 UTCGHSA enrichment
  39. 2026-08-12 13:51 UTCEPSS rescore
  40. 2026-08-11 21:14 UTCEG score recompute
  41. 2026-08-11 21:14 UTCVendor advisory
  42. 2026-08-11 21:14 UTCGHSA enrichment
  43. 2026-08-11 00:00 UTCEPSS rescore
  44. 2026-08-10 20:36 UTCVendor advisory
  45. 2026-08-10 20:36 UTCGHSA enrichment
  46. 2026-08-09 19:57 UTCEG score recompute
  47. 2026-08-09 19:57 UTCVendor advisory
  48. 2026-08-09 19:57 UTCGHSA enrichment
  49. 2026-08-09 13:46 UTCEPSS rescore
  50. 2026-08-08 19:19 UTCEG score recompute
  51. 2026-08-08 19:19 UTCVendor advisory
  52. 2026-08-08 19:19 UTCGHSA enrichment
  53. 2026-08-08 16:37 UTCEPSS rescore
  54. 2026-08-07 18:40 UTCEG score recompute
  55. 2026-08-07 18:40 UTCVendor advisory
  56. 2026-08-07 18:40 UTCGHSA enrichment
  57. 2026-08-06 18:00 UTCEG score recompute
  58. 2026-08-06 18:00 UTCVendor advisory
  59. 2026-08-06 18:00 UTCGHSA enrichment
  60. 2026-08-06 13:47 UTCEPSS rescore
  61. 2026-08-05 19:17 UTCEPSS rescore
  62. 2026-08-05 17:22 UTCVendor advisory
  63. 2026-08-05 17:21 UTCGHSA enrichment
  64. 2026-08-04 15:11 UTCEG score recompute
  65. 2026-08-04 15:11 UTCVendor advisory
  66. 2026-08-04 15:10 UTCGHSA enrichment
  67. 2026-08-04 15:10 UTCEPSS rescore
  68. 2026-08-04 10:39 UTCEPSS rescore
  69. 2026-08-03 10:36 UTCEPSS rescore
  70. 2026-08-03 07:57 UTCVendor advisory
  71. 2026-08-03 07:57 UTCGHSA enrichment
  72. 2026-08-02 04:48 UTCEG score recompute
  73. 2026-08-02 04:48 UTCVendor advisory
  74. 2026-08-02 04:48 UTCGHSA enrichment
  75. 2026-08-02 02:27 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-53018?
CVE-2026-53018 is a medium vulnerability published on June 24, 2026. 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:f2fsmetaaops ino:2…
When was CVE-2026-53018 disclosed?
CVE-2026-53018 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53018 actively exploited?
CVE-2026-53018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-53018?
CVE-2026-53018 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53018?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53018, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53018

Explore →

Is Your Infrastructure Affected by CVE-2026-53018?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs