LiveActive security incident?Get immediate response
CVE Record

CVE-2024-44942: f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC syzbot reports a f2fs bug as below: ------------[ cut here ]------------ kernel BUG at fs/f2fs/inline.c:258! CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0 RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258 Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 The root cause is: inline_data inode can be fuzzed, so that there may be valid blkaddr in its direct node, once f2fs triggers background GC to migrate the block, it will hit f2fs_bug_on() during dirty page writeback. Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC, so that, it can forbid migrating inline_data inode's data block for fixing.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel F2FS filesystem bug that can trigger a kernel BUG during background garbage collection. The business impact is most likely availability disruption on systems using F2FS, not confirmed data theft or remote compromise. Public sources do not provide a CVSS score or report active exploitation.

Executive priority

Schedule remediation through normal kernel patch cycles, with higher priority for F2FS-backed devices or systems handling removable or untrusted storage. There is no source-backed evidence of active exploitation, but kernel BUG conditions can still create service reliability risk.

Technical view

F2FS inline-data inode metadata can be malformed so a direct node contains a valid block address. During background garbage collection, F2FS may try to migrate that block and hit f2fs_bug_on() during dirty page writeback. The fix adds a sanity check for F2FS_INLINE_DATA during GC to prevent migrating inline-data inode blocks.

Likely exposure

Exposure is most relevant for Linux systems using F2FS on affected kernels. Systems not using or mounting F2FS are less likely to be exposed. The source bundle lists Linux kernel versions and stable commit references, but does not provide distro-specific package status.

Exploitation context

The report came from syzbot fuzzing and describes a fuzzed inline_data inode. The bundle marks KEV as false and provides no cited evidence of exploitation in the wild. Treat this as a kernel availability risk unless vendor advisories add more impact details.

Researcher notes

Key evidence is the upstream Linux kernel description and stable commits. The record lacks CVSS, CWE, exploit status, and distro package mappings. Validation should focus on F2FS usage, affected kernel lineage, and whether vendor kernels have backported the sanity check.

Mitigation direction

  • Apply Linux kernel updates containing the referenced F2FS stable fixes.
  • Check Linux distribution advisories for CVE-2024-44942 package status.
  • Prioritize systems that use or mount F2FS filesystems.
  • Avoid mounting untrusted or suspicious F2FS images until patched.
  • Monitor vendor guidance for any expanded impact or mitigation details.

Validation and detection

  • Inventory Linux hosts and identify those using F2FS.
  • Confirm kernel packages include the referenced stable fixes or vendor backports.
  • Review distribution changelogs for CVE-2024-44942 remediation.
  • Verify no critical workloads depend on unpatched F2FS mounts.
  • Track whether vendors publish severity, CVSS, or exploitability updates.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-44942 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux98e4da8ca301e062d79ae168c67e56f3c3de3ce4, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4unaffected
LinuxLinux3.8, 0, 6.6.47, 6.10.6, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.