CVE-2024-27033

What it actually does

Unnecessary f2fs_bug_on() in verify_blkaddr() triggers kernel panic when f2fs_is_valid_blkaddr() is fault-injected, allowing local fault injection or malformed block address conditions to crash the kernel.

Why it matters to the business

Unexpected system crashes on Linux hosts using f2fs can interrupt services, cause data unavailability, and require manual recovery or reboots.

How an attack unfolds

An attacker with local access or the ability to trigger fault injection into f2fs block address validation forces verify_blkaddr() to hit the bug_on, resulting in an immediate kernel panic.

How to fix it

Upgrade the Linux kernel to a version containing commit 0386408036bfc8b50296d9e544ff91c4d52af2db or later; apply the fix that removes the unnecessary f2fs_bug_on() call.

How to confirm the fix worked

Confirm the presence of commit 0386408036bfc8b50296d9e544ff91c4d52af2db in the kernel source; re-test fault injection into f2fs_is_valid_blkaddr() to verify no panic occurs.

Typical attack path

1. Gain local access or fault-injection capability on a system with f2fs
2. Trigger fault into f2fs_is_valid_blkaddr()
3. Invoke code path reaching verify_blkaddr()
4. Hit f2fs_bug_on() causing kernel panic

How to detect it

Search kernel panic logs and dmesg output for references to f2fs_bug_on, verify_blkaddr, or f2fs_is_valid_blkaddr failures.

• f2fs_bug_on
• verify_blkaddr
• f2fs_is_valid_blkaddr

What your security team should do

• Apply kernel updates containing the referenced commit as soon as possible
• Monitor kernel logs for f2fs-related panic messages
• Limit use of f2fs on systems where fault injection or untrusted block devices are possible