CVE-2024-33847: f2fs: compress: don't allow unaligned truncation on released compress inode
In the Linux kernel, the following vulnerability has been resolved:
f2fs: compress: don't allow unaligned truncation on released compress inode
f2fs image may be corrupted after below testcase:
- mkfs.f2fs -O extra_attr,compression -f /dev/vdb
- mount /dev/vdb /mnt/f2fs
- touch /mnt/f2fs/file
- f2fs_io setflags compression /mnt/f2fs/file
- dd if=/dev/zero of=/mnt/f2fs/file bs=4k count=4
- f2fs_io release_cblocks /mnt/f2fs/file
- truncate -s 8192 /mnt/f2fs/file
- umount /mnt/f2fs
- fsck.f2fs /dev/vdb
[ASSERT] (fsck_chk_inode_blk:1256) --> ino: 0x5 has i_blocks: 0x00000002, but has 0x3 blocks
[FSCK] valid_block_count matching with CP [Fail] [0x4, 0x5]
[FSCK] other corrupted bugs [Fail]
The reason is: partial truncation assume compressed inode has reserved
blocks, after partial truncation, valid block count may change w/o
.i_blocks and .total_valid_block_count update, result in corruption.
This patch only allow cluster size aligned truncation on released
compress inode for fixing.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel F2FS compression bug that can corrupt filesystem metadata after certain truncation behavior on released compressed files. The public record describes data integrity impact, not remote code execution or privilege escalation. No CVSS score is provided, and CISA KEV is false in the supplied bundle.
Executive priority
Handle through normal kernel patch management unless F2FS compression protects important production or embedded storage. Escalate priority for systems where filesystem corruption would affect availability, recovery, or device integrity.
Technical view
The F2FS compression path allowed unaligned truncation on a released compressed inode. Partial truncation could change valid block counts without updating i_blocks and total_valid_block_count, causing fsck failures and image corruption. The kernel fix restricts truncation to cluster-size-aligned operations for released compressed inodes.
Likely exposure
Exposure is most likely on Linux systems or products using F2FS with compression enabled and affected kernel builds. Systems not using F2FS compression are not shown as exposed by the supplied sources. Siemens has a referenced advisory, but product-specific impact is not included in this bundle.
Exploitation context
The supplied sources describe a reproducible corruption case and kernel fixes. They do not show active exploitation, weaponized tooling, remote attack paths, or inclusion in CISA KEV. Treat this as an integrity and availability risk until vendor guidance says otherwise.
Researcher notes
The record provides kernel commit references and a corruption rationale, but no CVSS, CWE, exploitability assessment, or detailed Siemens product scope. Analysis should stay focused on F2FS compressed inode truncation and avoid assuming broader Linux filesystem exposure.
Mitigation direction
Check Linux distribution and vendor advisories for CVE-2024-33847 fixes.
Update affected kernels to builds containing the referenced stable fixes.
Prioritize systems using F2FS compression on production or embedded storage.
Review Siemens SSA-265688 if Siemens products are in scope.
If no fixed build exists, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux hosts and appliances using F2FS filesystems.
Identify whether F2FS compression is enabled on those systems.
Compare running kernel builds against vendor fixed versions or referenced commits.
Review fsck or storage integrity alerts for F2FS corruption indicators.
Confirm distribution advisories list CVE-2024-33847 as remediated after patching.
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-33847 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.