CVE-2024-53220: f2fs: fix to account dirty data in __get_secs_required()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1acd73edbbfef2c3c5b43cba4006a7797eca7050, 6e58b2987960efcd917bc42da781cee256213618, 9313b85ddc120e2d2f0efaf86d0204d4c98d60b1.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 1acd73edbbfef2c3c5b43cba4006a7797eca7050, 6e58b2987960efcd917bc42da781cee256213618, 9313b85ddc120e2d2f0efaf86d0204d4c98d60b1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to account dirty data in __get_secs_required() It will trigger system panic w/ testcase in [1]: ------------[ cut here ]------------ kernel BUG at fs/f2fs/segment.c:2752! RIP: 0010:new_curseg+0xc81/0x2110 Call Trace: f2fs_allocate_data_block+0x1c91/0x4540 do_write_page+0x163/0xdf0 f2fs_outplace_write_data+0x1aa/0x340 f2fs_do_write_data_page+0x797/0x2280 f2fs_write_single_data_page+0x16cd/0x2190 f2fs_write_cache_pages+0x994/0x1c80 f2fs_write_data_pages+0x9cc/0xea0 do_writepages+0x194/0x7a0 filemap_fdatawrite_wbc+0x12b/0x1a0 __filemap_fdatawrite_range+0xbb/0xf0 file_write_and_wait_range+0xa1/0x110 f2fs_do_sync_file+0x26f/0x1c50 f2fs_sync_file+0x12b/0x1d0 vfs_fsync_range+0xfa/0x230 do_fsync+0x3d/0x80 __x64_sys_fsync+0x37/0x50 x64_sys_call+0x1e88/0x20d0 do_syscall_64+0x4b/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e The root cause is if checkpoint_disabling and lfs_mode are both on, it will trigger OPU for all overwritten data, it may cost more free segment than expected, so f2fs must account those data correctly to calculate cosumed free segments later, and return ENOSPC earlier to avoid run out of free segment during block allocation. [1] https://lore.kernel.org/fstests/20241015025106.3203676-1-chao@kernel.org/
- Published
- Dec 27, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.20affected
- 4354994f097d068a894aa1a0860da54571df3582 and later · before 6e58b2987960efcd917bc42da781cee256213618affected · git
- 4354994f097d068a894aa1a0860da54571df3582 and later · before f1b8bfe8d2f2fdf905d37c174d5bc1cd2b6910c5affected · git
- 4354994f097d068a894aa1a0860da54571df3582 and later · before 9313b85ddc120e2d2f0efaf86d0204d4c98d60b1affected · git
- 4354994f097d068a894aa1a0860da54571df3582 and later · before e812871c068cc0f91ff9f5cee87d00df1c44aae4affected · git
- 4354994f097d068a894aa1a0860da54571df3582 and later · before 1acd73edbbfef2c3c5b43cba4006a7797eca7050affected · git
- before 4.20not affected · semver
- 6.1.120 and later · up to and including 6.1.*not affected · semver
- 6.6.64 and later · up to and including 6.6.*not affected · semver
- 6.11.11 and later · up to and including 6.11.*not affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.20 and later · before 6.1.120
- linux linux kernel6.2 and later · before 6.6.64
- linux linux kernel6.7 and later · before 6.11.11
- linux linux kernel6.12 and later · before 6.12.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.123-1 | 6.1.123-1 |
| Debian:13 | linux | before 6.12.3-1 | 6.12.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-53215Dec 27, 2024 · svcrdma: fix miss destroy percpu_counter in svc_rdma_proc_init()22Monitor
- ← EarlierCVE-2024-53218Dec 27, 2024 · f2fs: fix race in concurrent f2fs_stop_gc_thread31Monitor
- Later →CVE-2024-53221Dec 27, 2024 · f2fs: fix null-ptr-deref in f2fs_submit_page_bio()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1acd73edbbfef2c3c5b43cba4006a7797eca7050 | Vendor (CNA) |
| Linux Linux | 6e58b2987960efcd917bc42da781cee256213618 | Vendor (CNA) |
| Linux Linux | 9313b85ddc120e2d2f0efaf86d0204d4c98d60b1 | Vendor (CNA) |
| Linux Linux | e812871c068cc0f91ff9f5cee87d00df1c44aae4 | Vendor (CNA) |
| Linux Linux | f1b8bfe8d2f2fdf905d37c174d5bc1cd2b6910c5 | Vendor (CNA) |
| debian:linux | 6.1.123-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/6e58b2987960efcd917bc42da781cee256213618
- git.kernel.org/stable/c/9313b85ddc120e2d2f0efaf86d0204d4c98d60b1
- git.kernel.org/stable/c/e812871c068cc0f91ff9f5cee87d00df1c44aae4
- git.kernel.org/stable/c/f1b8bfe8d2f2fdf905d37c174d5bc1cd2b6910c5
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.