Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2024-43859 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

f2fs: fix to truncate preallocated blocks in f2fs_file_open()

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to truncate preallocated blocks in f2fs_file_open()

chenyuwen reports a f2fs bug as below:

Unable to handle kernel NULL pointer dereference at virtual address 0000000000000011

fscrypt_set_bio_crypt_ctx+0x78/0x1e8

f2fs_grab_read_bio+0x78/0x208

f2fs_submit_page_read+0x44/0x154

f2fs_get_read_data_page+0x288/0x5f4

f2fs_get_lock_data_page+0x60/0x190

truncate_partial_data_page+0x108/0x4fc

f2fs_do_truncate_blocks+0x344/0x5f0

f2fs_truncate_blocks+0x6c/0x134

f2fs_truncate+0xd8/0x200

f2fs_iget+0x20c/0x5ac

do_garbage_collect+0x5d0/0xf6c

f2fs_gc+0x22c/0x6a4

f2fs_disable_checkpoint+0xc8/0x310

f2fs_fill_super+0x14bc/0x1764

mount_bdev+0x1b4/0x21c

f2fs_mount+0x20/0x30

legacy_get_tree+0x50/0xbc

vfs_get_tree+0x5c/0x1b0

do_new_mount+0x298/0x4cc

path_mount+0x33c/0x5fc

__arm64_sys_mount+0xcc/0x15c

invoke_syscall+0x60/0x150

el0_svc_common+0xb8/0xf8

do_el0_svc+0x28/0xa0

el0_svc+0x24/0x84

el0t_64_sync_handler+0x88/0xec

It is because inode.i_crypt_info is not initialized during below path:

  • mount
  • f2fs_fill_super
  • f2fs_disable_checkpoint
  • f2fs_gc
  • f2fs_iget
  • f2fs_truncate

So, let's relocate truncation of preallocated blocks to f2fs_file_open(),

after fscrypt_file_open().

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2024-43859 is recorded against 3 packages.

  • :linux-kernel: (from :0 up to :2026-03-05)
  • kernel (from 6.7.0 up to 6.10.3)
  • linux-kernel (from 6.7 up to 6.10.3)

Timeline and source

Published on 1 March 2026 and last revised on 20 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

source.android.com (Advisory)
android.googlesource.com (Fix)
android.googlesource.com (Fix)

Other advisories for this package

:linux-kernel: has other advisories on record. If you are patching this one, these are worth checking on the same host:

CVE-2024-43859 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2026-03-01
Updated 2026-08-20
Modified 2026-08-20

Affected Packages

Software From version Fixed in
:linux-kernel: :0 :2026-03-05
kernel 6.7.0 6.10.3
linux-kernel 6.7 6.10.3

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-43859 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024
✓