Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain physical or supply-chain access to NAND flash
-
DeliveryCorrupt or wear-induce a checkpoint page on flash media
-
ExploitBoot or remount device running Zephyr v4.4.0 with Dhara FTL
-
Executiondisk_ftl_access_init() triggers dhara_map_resume() checkpoint scan
-
Persistdhara_nand_read() dereferences NULL err pointer on flash error
-
ImpactKernel fault crashes device
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Null pointer safety, defensive checks
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires all of the following conditions simultaneously: the target device runs Zephyr v4.4.0 with the Dhara FTL disk driver compiled and enabled; a NAND flash device is managed by the Dhara FTL layer; and one of the probed Dhara journal checkpoint pages returns a flash read error - specifically uncorrectable ECC, a bad block, or a hardware controller error - during the journal-resume binary search executed at FTL initialization (disk_ftl_access_init() → dhara_map_resume()). The flash error condition can arise from natural media wear, hardware fault, or deliberate corruption of the on-flash image. Exploitation is further limited by: a local-only attack vector with no network path; high attack complexity requiring a flash error on a specific checkpoint page at the precise moment of mount; need for physical or supply-chain-level influence over flash media content; and restriction to the single Zephyr version that introduced the driver. |
| Impact | The CVSS 3.1 base score of 4.7 (Medium) with vector AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H accurately reflects the constrained threat model: local-only attack vector, high exploitation complexity, and availability-only impact. The AC:H designation is appropriate because a flash read error must occur specifically on a checkpoint page during the binary search scan at initialization - a condition that cannot be reliably forced from software alone and typically requires physical media access, induced wear, or a crafted on-flash image. No EPSS score was provided in the input data. The CVE is not listed in the CISA KEV catalog, and no public proof-of-concept code has been identified. In practice, risk is bounded to Zephyr v4.4.0 deployments using Dhara FTL-managed NAND flash with degraded, corrupted, or adversarially prepared media - limiting the realistic attacker profile to physical access or supply-chain actors. There is no confidentiality or integrity impact, and the scope remains unchanged within the affected system. |
| Exploit ScenarioDerived | An attacker with physical access to a Zephyr v4.4.0 device - or one who can provision a crafted NAND flash image during manufacturing or supply-chain handling - induces an uncorrectable ECC error or bad block on one of the Dhara journal checkpoint pages. When the device boots and the FTL disk initializes, dhara_map_resume() performs a binary search over checkpoint pages, passing NULL as the error pointer; the driver dereferences NULL upon encountering the flash error, faulting the kernel and crashing the device. No public exploit code exists for this vulnerability at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 07, 2026
Kernel denial-of-service in Zephyr RTOS v4.4.0's Dhara flash translation layer driver crashes the system during FTL disk initialization when a flash error coincides with the journal-resume checkpoint scan. The driver's dhara_nand_read/erase/prog/copy callbacks unconditionally dereference the caller-supplied err pointer, but the upstream Dhara library legitimately passes NULL during its binary search in find_last_checkblock(), triggering a NULL write and kernel fault. No public exploit code has been identified and this CVE is absent from the CISA KEV catalog; exploitation is gated on specific flash media conditions (uncorrectable ECC, bad block, or induced fault) occurring on a checkpoint page at mount time, constraining real-world risk to physical or supply-chain threat models.
RemediationAI
The upstream fix is available as commit a8371b0d4719efe37a66e2abb618ad9b81792212 in the Zephyr GitHub repository (https://github.com/zephyrproject-rtos/zephyr/commit/a8371b0d4719efe37a66e2abb618ad9b81792212), replacing direct err pointer writes with the NULL-safe dhara_set_error() helper. A formally tagged patched release version has not been independently confirmed from the available reference data; downstream integrators should apply the patch commit directly and monitor the Zephyr release channel and advisory at GHSA-q28v-3729-f82g. As a compensating control, disabling the Dhara FTL disk driver via its Kconfig option eliminates the vulnerable code path entirely, at the cost of losing Dhara FTL-managed NAND flash support. Where the driver must remain active, validating on-flash image integrity at provisioning time and restricting physical access to flash storage reduces the probability of triggering the vulnerable flash-error condition.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Zephyr RTOS (CPE: cpe:2.3:a:zephyrproject:zephyr:*:*:*:*:*:*:*:*) introduced the Dhara flash translation layer disk driver in v4.4.0 via drivers/disk/ftl_dhara.c. The Dhara library is an open-source FTL providing journaling and wear-leveling for raw NAND flash. CWE-476 (NULL Pointer Dereference) is the root cause: the Zephyr driver implements dhara_nand_* callbacks that write the error code directly to the err pointer (e.g., *err = DHARA_E_ECC) without first checking for NULL. The upstream library's find_last_checkblock() performs a binary search during journal resume via dhara_map_resume(), calling find_checkblock(j, mid, &found, NULL) - propagating NULL into dhara_nand_read() as the err argument. This execution path is exercised at every FTL disk mount via disk_ftl_access_init(). The fix in commit a8371b0d4719efe37a66e2abb618ad9b81792212 routes all error assignments through the library's NULL-safe dhara_set_error() helper, eliminating the dereference.
Know when Checkpoint gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Local vector and AC:H reflect the flash-error-at-checkpoint prerequisite; PR:L covers application-level disk mount access; C and I are N as only kernel availability is impacted.
Primary rating from Vendor (zephyr).
CVSS VectorNVD
DescriptionNVD
The Dhara flash translation layer disk driver (drivers/disk/ftl_dhara.c) implemented the dhara_nand_ callbacks so that, on a flash error, the error code was written unconditionally through the caller-supplied dhara_error_t err pointer (e.g. *err = DHARA_E_ECC in dhara_nand_read, and similar in dhara_nand_erase/prog/copy). The upstream Dhara library calls these callbacks with err == NULL along its journal-resume binary search: find_last_checkblock() invokes find_checkblock(j, mid, &found, NULL), which forwards the NULL pointer into dhara_nand_read(). This path runs during disk_ftl_access_init() -> dhara_map_resume() whenever the FTL disk is mounted/initialised. If a flash read error (uncorrectable ECC, bad block, controller error) occurs on one of the probed checkpoint pages, the driver dereferences and writes to NULL, faulting the kernel (denial of service). The trigger is conditioned on the NAND medium content/health, which can be influenced by media wear, induced faults, or a corrupted/crafted on-flash image. The fix routes all error assignments through the library's NULL-safe dhara_set_error() helper. Affects Zephyr v4.4.0, where the driver was introduced.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A null pointer dereference occurs when a program attempts to access memory through a pointer that has been set to NULL (address 0x0).
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Checkpoint
View allGNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which
Potentially allowing an attacker to read certain information on Check Point Security Gateways once connected to the inte
GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of
backend/comics/comics-document.c (aka the comic book backend) in GNOME Evince before 3.24.1 allows remote attackers to e
Remote code execution in Check Point Quantum Security Gateway arises from improper certificate trust validation during V
Authentication bypass in the Check Point SmartConsole login process lets an unauthenticated remote attacker mint a valid
Authentication bypass in Check Point Quantum Security Gateway and Spark Firewalls allows unauthenticated remote attacker
Unauthenticated attackers who can reach the file-upload interface of Check Point Management Server can combine directory
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. Rated med
Remote code execution in Check Point Quantum Security Gateway and Quantum Security Management stems from a heap-based bu
Unauthenticated remote code execution affects Check Point Quantum Security Management, where a stack-based buffer overfl
The huggingface/transformers library is vulnerable to arbitrary code execution through deserialization of untrusted data
EUVD-2026-42037
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB