CVE-2024-42297: f2fs: fix to don't dirty inode for readonly filesystem
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.24% (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 192b8fb8d1c8ca3c87366ebbef599fa80bb626b8, 2434344559f6743efb3ac15d11af9a0db9543bd3, 2d2916516577f2239b3377d9e8d12da5e6ccdfcf; CBL Mariner 2.0 ARM 5.15.167.1-2; CBL Mariner 2.0 x64 5.15.167.1-2.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 192b8fb8d1c8ca3c87366ebbef599fa80bb626b8, 2434344559f6743efb3ac15d11af9a0db9543bd3, 2d2916516577f2239b3377d9e8d12da5e6ccdfcf; CBL Mariner 2.0 ARM 5.15.167.1-2; CBL Mariner 2.0 x64 5.15.167.1-2 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 don't dirty inode for readonly filesystem syzbot reports f2fs bug as below: kernel BUG at fs/f2fs/inode.c:933! RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933 Call Trace: evict+0x2a4/0x620 fs/inode.c:664 dispose_list fs/inode.c:697 [inline] evict_inodes+0x5f8/0x690 fs/inode.c:747 generic_shutdown_super+0x9d/0x2c0 fs/super.c:675 kill_block_super+0x44/0x90 fs/super.c:1667 kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894 deactivate_locked_super+0xc1/0x130 fs/super.c:484 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256 task_work_run+0x24a/0x300 kernel/task_work.c:180 ptrace_notify+0x2cd/0x380 kernel/signal.c:2399 ptrace_report_syscall include/linux/ptrace.h:411 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline] syscall_exit_work kernel/entry/common.c:251 [inline] syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline] syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296 do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88 entry_SYSCALL_64_after_hwframe+0x63/0x6b The root cause is: - do_sys_open - f2fs_lookup - __f2fs_find_entry - f2fs_i_depth_write - f2fs_mark_inode_dirty_sync - f2fs_dirty_inode - set_inode_flag(inode, FI_DIRTY_INODE) - umount - kill_f2fs_super - kill_block_super - generic_shutdown_super - sync_filesystem : sb is readonly, skip sync_filesystem() - evict_inodes - iput - f2fs_evict_inode - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE)) : trigger kernel panic When we try to repair i_current_depth in readonly filesystem, let's skip dirty inode to avoid panic in later f2fs_evict_inode().
- Published
- Aug 17, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 6.1.103
- linux linux kernel6.2 and later · before 6.6.44
- linux linux kernel6.7 and later · before 6.10.3
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
- 3.8affected
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 2d2916516577f2239b3377d9e8d12da5e6ccdfcfaffected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 54162974aea37a8cae00742470a78c7f6bd6f915affected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 54bc4e88447e385c4d4ffa85d93e0dce628fcfa6affected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1affected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 9ce8135accf103f7333af472709125878704fdd4affected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before e62ff092a42f4a1bae3b310cf46673b4f3aac3b5affected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 2434344559f6743efb3ac15d11af9a0db9543bd3affected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 192b8fb8d1c8ca3c87366ebbef599fa80bb626b8affected · git
- before 3.8not affected · semver
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.106-1 | 6.1.106-1 |
| Debian:13 | linux | before 6.10.3-1 | 6.10.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-42295Aug 17, 2024 · nilfs2: handle inconsistent state in nilfs_btnode_create_block()22Monitor
- ← EarlierCVE-2024-42296Aug 17, 2024 · f2fs: fix return value of f2fs_convert_inline_inode()22Monitor
- Later →CVE-2024-42298Aug 17, 2024 · ASoC: fsl: fsl_qmc_audio: Check devm_kasprintf() returned value22Monitor
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 | 192b8fb8d1c8ca3c87366ebbef599fa80bb626b8 | Vendor (CNA) |
| Linux Linux | 2434344559f6743efb3ac15d11af9a0db9543bd3 | Vendor (CNA) |
| Linux Linux | 2d2916516577f2239b3377d9e8d12da5e6ccdfcf | Vendor (CNA) |
| Linux Linux | 54162974aea37a8cae00742470a78c7f6bd6f915 | Vendor (CNA) |
| Linux Linux | 54bc4e88447e385c4d4ffa85d93e0dce628fcfa6 | Vendor (CNA) |
| Linux Linux | 9ce8135accf103f7333af472709125878704fdd4 | Vendor (CNA) |
| Linux Linux | e62ff092a42f4a1bae3b310cf46673b4f3aac3b5 | Vendor (CNA) |
| Linux Linux | ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1 | Vendor (CNA) |
| CBL Mariner 2.0 ARM | 5.15.167.1-2 · kernel | Microsoft (MSRC) |
| CBL Mariner 2.0 x64 | 5.15.167.1-2 · kernel | Microsoft (MSRC) |
| debian:linux | 6.1.106-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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1290 · Aug 19, 2024(Linux Kernel Güvenlik Bildirimi)
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/2434344559f6743efb3ac15d11af9a0db9543bd3
- git.kernel.org/stable/c/2d2916516577f2239b3377d9e8d12da5e6ccdfcf
- git.kernel.org/stable/c/54162974aea37a8cae00742470a78c7f6bd6f915
- git.kernel.org/stable/c/54bc4e88447e385c4d4ffa85d93e0dce628fcfa6
- git.kernel.org/stable/c/9ce8135accf103f7333af472709125878704fdd4
- git.kernel.org/stable/c/e62ff092a42f4a1bae3b310cf46673b4f3aac3b5
- git.kernel.org/stable/c/ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1
- lists.debian.org/debian-lts-announce/2024/10/msg00003.html
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.