LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42273: f2fs: assign CURSEG_ALL_DATA_ATGC if blkaddr is valid

In the Linux kernel, the following vulnerability has been resolved: f2fs: assign CURSEG_ALL_DATA_ATGC if blkaddr is valid mkdir /mnt/test/comp f2fs_io setflags compression /mnt/test/comp dd if=/dev/zero of=/mnt/test/comp/testfile bs=16k count=1 truncate --size 13 /mnt/test/comp/testfile In the above scenario, we can get a BUG_ON. kernel BUG at fs/f2fs/segment.c:3589! Call Trace: do_write_page+0x78/0x390 [f2fs] f2fs_outplace_write_data+0x62/0xb0 [f2fs] f2fs_do_write_data_page+0x275/0x740 [f2fs] f2fs_write_single_data_page+0x1dc/0x8f0 [f2fs] f2fs_write_multi_pages+0x1e5/0xae0 [f2fs] f2fs_write_cache_pages+0xab1/0xc60 [f2fs] f2fs_write_data_pages+0x2d8/0x330 [f2fs] do_writepages+0xcf/0x270 __writeback_single_inode+0x44/0x350 writeback_sb_inodes+0x242/0x530 __writeback_inodes_wb+0x54/0xf0 wb_writeback+0x192/0x310 wb_workfn+0x30d/0x400 The reason is we gave CURSEG_ALL_DATA_ATGC to COMPR_ADDR where the page was set the gcing flag by set_cluster_dirty().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-42273 is a Linux kernel F2FS filesystem flaw that can trigger a kernel BUG during specific compressed-file writeback behavior. The public record does not provide CVSS, impact rating, or evidence of exploitation. Business urgency depends on whether systems use writable F2FS filesystems, especially with compression enabled.

Executive priority

Treat this as targeted infrastructure hygiene, not an emergency, unless production systems use writable F2FS. Prioritize patching affected Linux kernels through normal maintenance, with faster handling for devices or servers where local users, containers, or workloads can write to F2FS volumes.

Technical view

The issue is in Linux F2FS segment handling. A valid block address path can assign CURSEG_ALL_DATA_ATGC in a case involving compressed data pages and garbage-collection state, leading to BUG_ON in fs/f2fs/segment.c during writeback. Stable kernel commits are referenced as the resolution sources.

Likely exposure

Most relevant exposure is Linux systems that mount F2FS filesystems and allow local write activity, particularly where F2FS compression is enabled. Servers using ext4, XFS, or other filesystems are less likely to be affected by this specific bug. The supplied version metadata is incomplete and should be verified against vendor kernels.

Exploitation context

The bundle shows no CISA KEV listing and no cited evidence of active exploitation. The described trigger requires filesystem-level operations on an F2FS compressed directory or file path. The likely practical concern is local denial of service or system instability, but the public bundle does not state a confirmed impact class.

Researcher notes

The public record gives a concrete kernel BUG trace and upstream stable references but lacks CVSS, CWE, exploit status, and a precise affected-version narrative. Validate exposure through actual filesystem use and distribution kernel advisories rather than relying only on the CVE version list.

Mitigation direction

  • Identify Linux hosts using F2FS, especially writable or compressed F2FS volumes.
  • Apply kernel updates from the relevant distribution or vendor advisory.
  • For Debian LTS systems, review and apply the referenced Debian announcement.
  • Map running kernels to the referenced stable fix commits where vendor guidance is unavailable.
  • Restrict untrusted local write access to affected F2FS volumes until patched.

Validation and detection

  • Inventory mounted filesystems and flag hosts using F2FS.
  • Check whether F2FS compression is enabled on relevant volumes.
  • Compare running kernel versions with vendor fixed-kernel guidance.
  • Confirm patched kernels include the referenced upstream stable commits.
  • Review system logs for kernel BUG reports involving f2fs segment writeback.
Prepared
Confidence
medium
Sources
7

Public sources used

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-42273 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
2ADP providers
6Source 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
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7c972c89457511007dfc933814c06786905e515c, 417b8a91f4e8831cadaf85c3f15c6991c1f54dde, 4961acdd65c956e97c1a000c82d91a8c1cdbe44b, 4961acdd65c956e97c1a000c82d91a8c1cdbe44b, 7ea0f29d9fd84905051be020c0df7d557e286136, b8094c0f1aae329b1c60a275a780d6c2c9ff7aa3, 6.1.77, 6.6.16, 5.15.149, 6.7.4unaffected
LinuxLinux6.8, 0, 6.1.104, 6.6.45, 6.10.4, 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.