VulnerabilityPublished 3 Dec 2025

CVE-2025-54326: NULL Pointer Dereference

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2025-54326, organizations should: 1) Monitor Samsung and mobile device vendors for official patches or firmware updates addressing this vulnerability and apply them promptly. 2) Restrict network access to device management interfaces and camera-related services to trusted networks and users only, reducing exposure to remote exploitation. 3) Employ mobile device management (MDM) solutions to enforce security policies and quickly deploy updates across the device fleet. 4) Conduct regular security assessments and penetration tests focusing on mobile device drivers and hardware interfaces to detect similar vulnerabilities. 5) Educate users and administrators about the risks of using untrusted networks or applications that might trigger the vulnerability. 6) Consider temporary disabling or limiting camera functionality on critical devices if patches are unavailable and the risk is deemed high. 7) Maintain incident response plans that include scenarios involving mobile device denial of service to ensure rapid recovery.

Description

CVE-2025-54326 is a high-severity vulnerability affecting the Camera device driver in Samsung Mobile Processors Exynos 1280 and 2200. It arises from an unnecessary registration of a hardware IP address, which can cause a NULL pointer dereference and lead to a denial of service (DoS). The vulnerability requires no authentication or user interaction and can be exploited remotely over the network. While no known exploits are currently in the wild, the impact is significant due to the potential to disrupt device availability. European organizations using devices with these processors, especially in sectors relying on mobile communications and embedded camera functionalities, could face operational disruptions. Mitigation involves applying vendor patches once available and restricting access to vulnerable device interfaces. Countries with high Samsung mobile device penetration and advanced mobile infrastructure, such as Germany, the UK, France, and Italy, are most likely to be affected. Given the ease of exploitation and the high impact on availability, this vulnerability is rated as high severity.

Impact

For European organizations, the primary impact of CVE-2025-54326 is the potential denial of service on mobile devices using the affected Samsung Exynos processors. This can disrupt communication, mobile data collection, and any business processes dependent on camera functionality, such as remote inspections, video conferencing, or security monitoring. Enterprises in sectors like telecommunications, healthcare, manufacturing, and public safety that deploy Samsung-based mobile devices may experience operational interruptions. The inability to use camera features could also affect user productivity and customer-facing services. While the vulnerability does not compromise data confidentiality or integrity, the loss of availability can lead to reputational damage and financial losses, especially if exploited at scale or during critical operations. The lack of known exploits currently reduces immediate risk but does not eliminate the threat, as attackers may develop exploits given the low complexity of triggering a NULL pointer dereference remotely.

Summary

CVE-2025-54326 is a vulnerability identified in the Camera device driver of Samsung Mobile Processors Exynos 1280 and 2200. The root cause is the unnecessary registration of a hardware IP address within the driver, which leads to a NULL pointer dereference when the system attempts to access or manipulate this invalid pointer. This results in a denial of service condition, effectively crashing or disabling the camera functionality on affected devices. The vulnerability is exploitable remotely without requiring any privileges or user interaction, as indicated by the CVSS vector (AV:N/AC:L/PR:N/UI:N). The impact is limited to availability, with no confidentiality or integrity loss reported. The weakness corresponds to CWE-476 (NULL Pointer Dereference), a common programming error that can cause system instability. Although no patches or exploits have been reported yet, the vulnerability's presence in widely used mobile processors makes it a significant concern. The denial of service could disrupt critical mobile applications relying on camera input, affecting both consumer and enterprise users. The vulnerability was reserved in July 2025 and published in December 2025, indicating recent discovery and disclosure.

CWE-476NULL Pointer Dereference (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #13OWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product dereferences a pointer that it expects to be valid but is NULL.
Implementation
For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
Requirements
Select a programming language that is not susceptible to these issues.
Implementation
Check the results of all functions that return a value and verify that the value is non-null before acting upon it.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 10 Dec 2025, 18:37 UTC

WeaknessesCWE-476

Technical details

References

Community reviews

Related threats