BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-43859High confidence

f2fs: fix to truncate preallocated blocks in f2fs_file_open()

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

14 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-40509

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

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().

What

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().

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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().

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-476
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0569Google Android: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Google Android ausnutzen, um sich erweiterte Berechtigungen zu verschaffen, beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu verursachen, vertrauliche Informationen offenzulegen oder andere nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-1875Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder unbekannte Auswirkungen zu erzielen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0231Multiples vulnérabilités dans Google Android

t été découvertes dans Google Android. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une élévation de privilèges et une atteinte à la confidentialité des données. Google indique que la vulnérabilité CVE-2026-21385 est activement exploitée. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Google Android du 02 mars 2026 https://source.android.com/docs/security/bulletin/2026/2026-03-01?hl=fr Référence CVE CVE-2024-43766 https://www.cve.org/CVERecord?id=CVE-2024-43766 Référence CVE CVE-2024-43859 https://www.cve.org/CVERecord?id=CVE-2024-43859 Référence CVE CVE-2025-10865 https://www.cve.org/CVERecord?id=CVE-2025-10865 Référence CVE CVE-2025-13952 https://www.cve.org/CVERecord?id=CVE-2025-13952 Référence CVE CVE-2025-20760 https://www.cve.org/CVERecord?id=CVE-2025-20760 Référence CVE CVE-2025-20761 https://www.cve.org/CVERecord?id=CVE-2025-20761 Référence CVE CVE-2025-20762 https://www.cve.org/CVERecord?id=CVE-2025-20762 Référence CVE CVE-2025-20793 https://www.cve.org/CVERecord?id=CVE-2025-20793 Référence CVE CVE-2025-20794 https://www.cve.org/CVERecord?id=CVE-2025-20794 Référence CVE CVE-2025-20795 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0022Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-43847 Référence CVE CVE-2024-43849 https://www.cve.org/CVERecord?id=CVE-2024-43849 Référence CVE CVE-2024-43850 https://www.cve.org/CVERecord?id=CVE-2024-43850 Référence CVE CVE-2024-43852 https://www.cve.org/CVERecord?id=CVE-2024-43852 Référence CVE CVE-2024-43853 https://www.cve.org/CVERecord?id=CVE-2024-43853 Référence CVE CVE-2024-43854 https://www.cve.org/CVERecord?id=CVE-2024-43854 Référence CVE CVE-2024-43856 https://www.cve.org/CVERecord?id=CVE-2024-43856 Référence CVE CVE-2024-43857 https://www.cve.org/CVERecord?id=CVE-2024-43857 Référence CVE CVE-2024-43858 https://www.cve.org/CVERecord?id=CVE-2024-43858 Référence CVE CVE-2024-43859 https://www.cve.org/CVERecord?id=CVE-2024-43859 Référence CVE CVE-2024-43860 https://www.cve.org/CVERecord?id=CVE-2024-43860 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-43863 https://www.cve.org/CVERecord?id=CVE-2024-43863 Référence CVE CVE-2024-43864 https://www.cve.org/CVERecord?id=CVE-2024-43864 Référence CVE CVE-2024-43866 https://www.cve.org/CVERecord?id=CVE-2024-43866 Référence CVE CVE-2024-43867 https://www.cve.org/CVERecord?id=CVE-2024-43867 Référence CVE CVE-2024-43868 https://www.cve.org/CVERecord?id=CVE-2024-43868 Référence CVE CVE-2024-43869 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0002Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2024-43842 Référence CVE CVE-2024-43846 https://www.cve.org/CVERecord?id=CVE-2024-43846 Référence CVE CVE-2024-43849 https://www.cve.org/CVERecord?id=CVE-2024-43849 Référence CVE CVE-2024-43851 https://www.cve.org/CVERecord?id=CVE-2024-43851 Référence CVE CVE-2024-43853 https://www.cve.org/CVERecord?id=CVE-2024-43853 Référence CVE CVE-2024-43854 https://www.cve.org/CVERecord?id=CVE-2024-43854 Référence CVE CVE-2024-43855 https://www.cve.org/CVERecord?id=CVE-2024-43855 Référence CVE CVE-2024-43856 https://www.cve.org/CVERecord?id=CVE-2024-43856 Référence CVE CVE-2024-43858 https://www.cve.org/CVERecord?id=CVE-2024-43858 Référence CVE CVE-2024-43859 https://www.cve.org/CVERecord?id=CVE-2024-43859 Référence CVE CVE-2024-43860 https://www.cve.org/CVERecord?id=CVE-2024-43860 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-43863 https://www.cve.org/CVERecord?id=CVE-2024-43863 Référence CVE CVE-2024-43866 https://www.cve.org/CVERecord?id=CVE-2024-43866 Référence CVE CVE-2024-43867 https://www.cve.org/CVERecord?id=CVE-2024-43867 Référence CVE CVE-2024-43868 https://www.cve.org/CVERecord?id=CVE-2024-43868 Référence CVE CVE-2024-43869 https://www.cve.org/CVERecord?id=CVE-2024-43869 Référence CVE CVE-2024-43870 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1080Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-43849 Référence CVE CVE-2024-43850 https://www.cve.org/CVERecord?id=CVE-2024-43850 Référence CVE CVE-2024-43852 https://www.cve.org/CVERecord?id=CVE-2024-43852 Référence CVE CVE-2024-43853 https://www.cve.org/CVERecord?id=CVE-2024-43853 Référence CVE CVE-2024-43854 https://www.cve.org/CVERecord?id=CVE-2024-43854 Référence CVE CVE-2024-43855 https://www.cve.org/CVERecord?id=CVE-2024-43855 Référence CVE CVE-2024-43856 https://www.cve.org/CVERecord?id=CVE-2024-43856 Référence CVE CVE-2024-43857 https://www.cve.org/CVERecord?id=CVE-2024-43857 Référence CVE CVE-2024-43858 https://www.cve.org/CVERecord?id=CVE-2024-43858 Référence CVE CVE-2024-43859 https://www.cve.org/CVERecord?id=CVE-2024-43859 Référence CVE CVE-2024-43860 https://www.cve.org/CVERecord?id=CVE-2024-43860 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-43863 https://www.cve.org/CVERecord?id=CVE-2024-43863 Référence CVE CVE-2024-43864 https://www.cve.org/CVERecord?id=CVE-2024-43864 Référence CVE CVE-2024-43866 https://www.cve.org/CVERecord?id=CVE-2024-43866 Référence CVE CVE-2024-43867 https://www.cve.org/CVERecord?id=CVE-2024-43867 Référence CVE CVE-2024-43868 https://www.cve.org/CVERecord?id=CVE-2024-43868 Référence CVE CVE-2024-43869 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0837Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2024-35943 Référence CVE CVE-2024-35966 https://www.cve.org/CVERecord?id=CVE-2024-35966 Référence CVE CVE-2024-40972 https://www.cve.org/CVERecord?id=CVE-2024-40972 Référence CVE CVE-2024-41016 https://www.cve.org/CVERecord?id=CVE-2024-41016 Référence CVE CVE-2024-41096 https://www.cve.org/CVERecord?id=CVE-2024-41096 Référence CVE CVE-2024-41098 https://www.cve.org/CVERecord?id=CVE-2024-41098 Référence CVE CVE-2024-42228 https://www.cve.org/CVERecord?id=CVE-2024-42228 Référence CVE CVE-2024-42314 https://www.cve.org/CVERecord?id=CVE-2024-42314 Référence CVE CVE-2024-43835 https://www.cve.org/CVERecord?id=CVE-2024-43835 Référence CVE CVE-2024-43859 https://www.cve.org/CVERecord?id=CVE-2024-43859 Référence CVE CVE-2024-43884 https://www.cve.org/CVERecord?id=CVE-2024-43884 Référence CVE CVE-2024-43892 https://www.cve.org/CVERecord?id=CVE-2024-43892 Référence CVE CVE-2024-44931 https://www.cve.org/CVERecord?id=CVE-2024-44931 Référence CVE CVE-2024-44938 https://www.cve.org/CVERecord?id=CVE-2024-44938 Référence CVE CVE-2024-44939 https://www.cve.org/CVERecord?id=CVE-2024-44939 Référence CVE CVE-2024-44940 https://www.cve.org/CVERecord?id=CVE-2024-44940 Référence CVE CVE-2024-44946 https://www.cve.org/CVERecord?id=CVE-2024-44946 Référence CVE CVE-2024-44947 https://www.cve.org/CVERecord?id=

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0074Kwetsbaarheden verholpen in Google Android en Samsung Mobile

Recent updates have addressed vulnerabilities in the Linux kernel, specifically related to f2fs, preventing NULL pointer dereference issues and mitigating multiple security risks in the Debian Linux Kernel.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Linux: d4dd19ec1ea0cf6532d65709325c42b1398614a8 < 5f04969136db674f133781626e0b692c5f2bf2f0, d4dd19ec1ea0cf6532d65709325c42b1398614a8 < f44a25a8bfe0c15d33244539696cd9119cf44d18, d4dd19ec1ea0cf6532d65709325c42b1398614a8 < 3ba0ae885215b325605ff7ebf6de12ac2adf204d, d4dd19ec1ea0cf6532d65709325c42b1398614a8 < 298b1e4182d657c3e388adcc29477904e9600ed5, 5.17
Fixed
Linux: < 5.17, 6.1.109 ≤ 6.1.*, 6.6.44 ≤ 6.6.*, 6.10.3 ≤ 6.10.*, 6.11 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 17 Aug 2024 · Last source change 11 May 2026, 20:31 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-40509
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-43859 · cve.blacktree.nl