Vulnerability CVE-2026-21144
Published Sources: HKCERT
What is affected, what to do
Multiple vulnerabilities were identified in Samsung Products. A remote attacker could exploit some of these vulnerabilities to trigger denial of service condition, elevation of privilege, security restriction bypass, sensitive information disclosure, remote code execution and data manipulation on the targeted system.
The available sources name no fixed version. Check the vendor guidance in the references below.
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Reserved
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 140.62 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
Multiple vulnerabilities were identified in Samsung Products. A remote attacker could exploit some of these vulnerabilities to trigger denial of service condition, elevation of privilege, security restriction bypass, sensitive information disclosure, remote code execution and data manipulation on the targeted system. Impact: Elevation of Privilege Remote Code Execution Denial of Service Information Disclosure Security Restriction Bypass Data Manipulation System / Technologies affected: Samsung mobile devices running Android 14, 15, 16, 17 Solutions: Before installation of the software, please visit the vendor web-site for more details. Apply fixes issued by the vendor: https://security.samsungmobile.com/securityUpdate.smsb
Source: HKCERT (CC BY 3.0 HK) · HKCERT rating: medium
Included in the same advisory
| High | CVE-2026-9040 | Mali GPU Kernel Driver allows denial of service or disclosure of sensitive information | 7.7 | — |
| High | CVE-2026-9034 | Mali GPU Userspace Driver allows access to already freed memory | 7.8 | — |
| High | CVE-2026-89774 | Linux Kernel: security vulnerability | 8.8 | — |
| High | CVE-2026-80604 | Linux Kernel: Out-of-Bounds Read | 8.8 | — |
| Not rated | CVE-2026-80013 | Vulnerability CVE-2026-80013 | — | — |
| Not rated | CVE-2026-66114 | Google Android: security vulnerability | — | — |
| Not rated | CVE-2026-66113 | Google Android: security vulnerability | — | — |
| High | CVE-2026-64560 | Linux Kernel: Race Condition | 7.8 | — |
| Medium | CVE-2026-64427 | Linux Kernel: NULL Pointer Dereference | 5.5 | — |
| Medium | CVE-2026-59048 | Google Android: Out-of-bounds Read | 5.5 | — |
| Medium | CVE-2026-59047 | Google Android: Improper Input Validation | 6.2 | — |
| Medium | CVE-2026-59046 | Google Android: Improper Input Validation | 6.2 | — |
| High | CVE-2026-59045 | Google Android: Race Condition | 7.4 | — |
| High | CVE-2026-59044 | Google Android: Use After Free | 8.4 | — |
| High | CVE-2026-59043 | Google Android: Race Condition | 7.4 | — |
| High | CVE-2026-59042 | Google Android: Race Condition | 7.4 | — |
| Medium | CVE-2026-59031 | Google Android: Protection Mechanism Failure | 6.2 | — |
| High | CVE-2026-59028 | Google Android: Confused Deputy | 8.4 | — |
| Medium | CVE-2026-59022 | Google Android: Incorrect Authorization | 5.5 | — |
| Medium | CVE-2026-59021 | Google Android: Improper Input Validation | 6.2 | — |
| Medium | CVE-2026-59020 | Google Android: Race Condition | 5.9 | — |
| High | CVE-2026-59016 | Google Android: Path Traversal | 8.4 | — |
| Medium | CVE-2026-59015 | Google Android: Confused Deputy | 4.0 | — |
| High | CVE-2026-59014 | Google Android: Out-of-bounds Write | 8.4 | — |
Show 170 more CVEs
| Medium | CVE-2026-59012 | Google Android: Missing Authorization | 5.5 | — |
| Medium | CVE-2026-59011 | Google Android: Incorrect Authorization | 5.5 | — |
| Medium | CVE-2026-59010 | Google Android: Improper Restriction of Operations within the Bounds of a Memory Buffer | 6.2 | — |
| Medium | CVE-2026-59008 | Google Android: Improper Input Validation | 6.2 | — |
| Medium | CVE-2026-59007 | Google Android: Out-of-bounds Read | 5.3 | — |
| Medium | CVE-2026-59006 | Google Android: User Interface (UI) Misrepresentation of Critical Information | 4.0 | — |
| High | CVE-2026-59005 | Google Android: Missing Authorization | 8.4 | — |
| High | CVE-2026-59004 | Google Android: Uncaught Exception | 8.4 | — |
| Medium | CVE-2026-59003 | Google Android: Missing Authorization | 4.0 | — |
| Medium | CVE-2026-59002 | Google Android: Information Disclosure | 4.6 | — |
| Not rated | CVE-2026-59001 | Google Android: Information Disclosure | — | — |
| High | CVE-2026-59000 | Google Android: Confused Deputy | 8.4 | — |
| Not rated | CVE-2026-58997 | Google Android: Out-of-Bounds Read | — | — |
| High | CVE-2026-58995 | Google Android: Heap-based Buffer Overflow | 8.4 | — |
| High | CVE-2026-58994 | Google Android: Missing Authorization | 8.4 | — |
| Not rated | CVE-2026-58990 | Google Android: Integer Overflow | — | — |
| High | CVE-2026-58989 | Google Android: Missing Authorization | 8.4 | — |
| High | CVE-2026-58986 | Google Android: Missing Authorization | 8.4 | — |
| Medium | CVE-2026-58985 | Google Android: Improper Input Validation | 6.2 | — |
| High | CVE-2026-58984 | Google Android: Use After Free | 8.4 | — |
| High | CVE-2026-58979 | Google Android: Protection Mechanism Failure | 8.4 | — |
| Medium | CVE-2026-58978 | Google Android: Protection Mechanism Failure | 6.8 | — |
| Medium | CVE-2026-58977 | Google Android: Improper Restriction of Operations within the Bounds of a Memory Buffer | 6.7 | — |
| Not rated | CVE-2026-58976 | Google Android: Information Disclosure | — | — |
| High | CVE-2026-58975 | Google Android: Improper Restriction of Operations within the Bounds of a Memory Buffer | 8.4 | — |
| High | CVE-2026-58974 | Google Android: Improper Privilege Management | 8.4 | — |
| Not rated | CVE-2026-58971 | Google Android: Out-of-Bounds Read | — | — |
| High | CVE-2026-58970 | Google Android: Confused Deputy | 8.4 | — |
| Not rated | CVE-2026-58969 | Google Android: Information Disclosure | — | — |
| Critical | CVE-2026-58968 | Google Android: Double Free | 9.8 | — |
| High | CVE-2026-58966 | Google Android: Stack-based Buffer Overflow | 8.4 | — |
| High | CVE-2026-58965 | Google Android: Confused Deputy | 8.4 | — |
| High | CVE-2026-58964 | Google Android: Improper Input Validation | 8.4 | — |
| High | CVE-2026-58962 | Google Android: Improper Privilege Management | 8.4 | — |
| High | CVE-2026-58961 | Google Android: Protection Mechanism Failure | 8.4 | — |
| Not rated | CVE-2026-58958 | Vulnerability CVE-2026-58958 | — | — |
| High | CVE-2026-58957 | Google Android: Confused Deputy | 8.4 | — |
| High | CVE-2026-58956 | Google Android: Protection Mechanism Failure | 8.4 | — |
| Medium | CVE-2026-58955 | Google Android: Improper Input Validation | 6.2 | — |
| Not rated | CVE-2026-58953 | Google Android: Heap-Based Buffer Overflow | — | — |
| Not rated | CVE-2026-58951 | Google Android: Information Disclosure | — | — |
| High | CVE-2026-58949 | Google Android: Stack-based Buffer Overflow | 7.5 | — |
| High | CVE-2026-58946 | Google Android: Protection Mechanism Failure | 8.4 | — |
| Not rated | CVE-2026-58945 | Google Android: Information Disclosure | — | — |
| High | CVE-2026-58944 | Google Android: Confused Deputy | 8.4 | — |
| High | CVE-2026-58943 | Google Android: Confused Deputy | 8.4 | — |
| High | CVE-2026-58942 | Google Android: Use After Free | 8.4 | — |
| Not rated | CVE-2026-58938 | Google Android: Improper Input Validation | — | — |
| Medium | CVE-2026-58937 | Google Android: Improper Input Validation | 6.2 | — |
| Critical | CVE-2026-58936 | Google Android: Use After Free | 9.8 | — |
| High | CVE-2026-58934 | Google Android: Protection Mechanism Failure | 8.4 | — |
| Medium | CVE-2026-58933 | Google Android: Out-of-bounds Read | 5.3 | — |
| High | CVE-2026-58886 | Google Android: User Interface (UI) Misrepresentation of Critical Information | 7.8 | — |
| High | CVE-2026-58885 | Google Android: Confused Deputy | 8.4 | — |
| High | CVE-2026-58884 | Google Android: Confused Deputy | 8.4 | — |
| Not rated | CVE-2026-58883 | Google Android: Denial of Service | — | — |
| Not rated | CVE-2026-58882 | Google Android: Out-of-Bounds Read | — | — |
| High | CVE-2026-58879 | Google Android: Out-of-bounds Write | 8.4 | — |
| Medium | CVE-2026-58877 | Google Android: Confused Deputy | 4.0 | — |
| Critical | CVE-2026-58876 | Google Android: Use After Free | 9.8 | — |
| Medium | CVE-2026-58875 | Google Android: Improper Input Validation | 6.2 | — |
| High | CVE-2026-58871 | Google Android: Heap-based Buffer Overflow | 8.4 | — |
| Not rated | CVE-2026-58870 | Google Android: Information Disclosure | — | — |
| Not rated | CVE-2026-58868 | Google Android: Heap-Based Buffer Overflow | — | — |
| High | CVE-2026-58867 | Google Android: Missing Authorization | 8.4 | — |
| High | CVE-2026-58866 | Google Android: Missing Authorization | 8.4 | — |
| High | CVE-2026-58857 | Google Android: Use After Free | 8.1 | — |
| High | CVE-2026-58853 | Google Android: Improper Restriction of Operations within the Bounds of a Memory Buffer | 7.5 | — |
| High | CVE-2026-58847 | Google Android: Protection Mechanism Failure | 8.4 | — |
| High | CVE-2026-58845 | Google Android: Integer Overflow or Wraparound | 8.4 | — |
| High | CVE-2026-58844 | Google Android: Out-of-bounds Read | 8.4 | — |
| Medium | CVE-2026-58838 | Google Android: Improper Input Validation | 4.0 | — |
| High | CVE-2026-58837 | Google Android: Protection Mechanism Failure | 8.4 | — |
| High | CVE-2026-58836 | Google Android: Protection Mechanism Failure | 7.8 | — |
| High | CVE-2026-58829 | Google Android: Use After Free | 8.4 | — |
| High | CVE-2026-58828 | Google Android: Use After Free | 8.4 | — |
| High | CVE-2026-58827 | Google Android: Use After Free | 8.4 | — |
| High | CVE-2026-58826 | Google Android: Use After Free | 8.4 | — |
| High | CVE-2026-58825 | Google Android: Use After Free | 8.4 | — |
| High | CVE-2026-58824 | Google Android: Improper Restriction of Operations within the Bounds of a Memory Buffer | 8.4 | — |
| Medium | CVE-2026-58821 | Google Android: SQL Injection | 6.2 | — |
| Medium | CVE-2026-58817 | Google Android: Improper Input Validation | 6.2 | — |
| High | CVE-2026-58814 | Google Android: Integer Overflow or Wraparound | 7.5 | — |
| Not rated | CVE-2026-57549 | Google Android: security vulnerability | — | — |
| Not rated | CVE-2026-57548 | Google Android: security vulnerability | — | — |
| Medium | CVE-2026-55292 | Google Android: Integer Overflow or Wraparound | 5.3 | — |
| High | CVE-2026-55289 | Google Android: Confused Deputy | 8.4 | — |
| High | CVE-2026-55288 | Google Android: Uncaught Exception | 8.4 | — |
| High | CVE-2026-55287 | Google Android: User Interface (UI) Misrepresentation of Critical Information | 8.4 | — |
| High | CVE-2026-55283 | Google Android: Use After Free | 8.4 | — |
| High | CVE-2026-55275 | Google Android: Use After Free | 8.4 | — |
| Medium | CVE-2026-55272 | Google Android: Improper Input Validation | 6.2 | — |
| High | CVE-2026-55271 | Google Android: Confused Deputy | 8.4 | — |
| Medium | CVE-2026-55264 | Google Android: Confused Deputy | 4.0 | — |
| High | CVE-2026-55263 | Google Android: User Interface (UI) Misrepresentation of Critical Information | 8.4 | — |
| High | CVE-2026-55262 | Google Android: Improper Input Validation | 8.4 | — |
| High | CVE-2026-55261 | Google Android: Missing Authorization | 8.4 | — |
| High | CVE-2026-55257 | Google Android: User Interface (UI) Misrepresentation of Critical Information | 8.4 | — |
| High | CVE-2026-53256 | Linux Kernel: Use After Free | 8.0 | — |
| Medium | CVE-2026-49935 | Google Android: Path Traversal | 4.0 | — |
| High | CVE-2026-49934 | Google Android: Improper Input Validation | 7.8 | — |
| High | CVE-2026-49931 | Google Android: Confused Deputy | 8.4 | — |
| Not rated | CVE-2026-49925 | Base: security vulnerability | — | — |
| Medium | CVE-2026-49924 | Google Android: Uncontrolled Resource Consumption | 6.2 | — |
| High | CVE-2026-49923 | Google Android: User Interface (UI) Misrepresentation of Critical Information | 8.4 | — |
| High | CVE-2026-49922 | Google Android: Confused Deputy | 8.4 | — |
| High | CVE-2026-46242 | Linux Kernel: Use After Free | 7.8 | — |
| High | CVE-2026-46232 | Linux Kernel: security vulnerability | 8.1 | — |
| Not rated | CVE-2026-45522 | Google Android: security vulnerability | — | — |
| High | CVE-2026-45514 | Google Android: Protection Mechanism Failure | 8.4 | — |
| High | CVE-2026-43284 | Linux Kernel: Write-what-where Condition | 8.8 | — |
| Critical | CVE-2026-31533 | Linux Kernel: Use After Free | 9.8 | — |
| High | CVE-2026-28665 | Google Android: Improper Input Validation | 8.4 | — |
| Medium | CVE-2026-28645 | Google Android: Protection Mechanism Failure | 6.8 | — |
| Medium | CVE-2026-28643 | Google Android: Improper Input Validation | 6.2 | — |
| Medium | CVE-2026-28632 | Google Android: Protection Mechanism Failure | 4.0 | — |
| Not rated | CVE-2026-28621 | Google Android: Information Disclosure | — | — |
| High | CVE-2026-28597 | Google Android: Improper Input Validation | 8.4 | — |
| High | CVE-2026-28588 | Google Android: Improper Access Control | 8.4 | — |
| Low | CVE-2026-28586 | Google Android: Improper Privilege Management | 3.3 | — |
| High | CVE-2026-28580 | Google Android: Classic Buffer Overflow | 7.8 | — |
| High | CVE-2026-25302 | Improper Verification of Cryptographic Signature in Boot | 7.1 | — |
| Not rated | CVE-2026-25287 | Google Android: security vulnerability | — | — |
| Not rated | CVE-2026-25286 | Google Android: security vulnerability | — | — |
| Not rated | CVE-2026-25285 | Google Android: security vulnerability | — | — |
| Critical | CVE-2026-23240 | Linux Kernel: Race Condition | 9.8 | — |
| High | CVE-2026-23184 | Linux Kernel: Use-After-Free | 7.8 | — |
| Not rated | CVE-2026-21158 | Vulnerability CVE-2026-21158 | — | — |
| Not rated | CVE-2026-21156 | Vulnerability CVE-2026-21156 | — | — |
| Not rated | CVE-2026-21155 | Vulnerability CVE-2026-21155 | — | — |
| Not rated | CVE-2026-21154 | Vulnerability CVE-2026-21154 | — | — |
| Not rated | CVE-2026-21153 | Vulnerability CVE-2026-21153 | — | — |
| Not rated | CVE-2026-21152 | Vulnerability CVE-2026-21152 | — | — |
| Not rated | CVE-2026-21151 | Vulnerability CVE-2026-21151 | — | — |
| Not rated | CVE-2026-21150 | Vulnerability CVE-2026-21150 | — | — |
| Not rated | CVE-2026-21149 | Vulnerability CVE-2026-21149 | — | — |
| Not rated | CVE-2026-21148 | Vulnerability CVE-2026-21148 | — | — |
| Not rated | CVE-2026-21147 | Vulnerability CVE-2026-21147 | — | — |
| Not rated | CVE-2026-21146 | Vulnerability CVE-2026-21146 | — | — |
| Not rated | CVE-2026-21145 | Vulnerability CVE-2026-21145 | — | — |
| Not rated | CVE-2026-21143 | Vulnerability CVE-2026-21143 | — | — |
| Not rated | CVE-2026-21142 | Vulnerability CVE-2026-21142 | — | — |
| Not rated | CVE-2026-21141 | Vulnerability CVE-2026-21141 | — | — |
| High | CVE-2026-20565 | MediaTek chipset: Out-of-bounds Write | 8.4 | — |
| Medium | CVE-2026-20564 | MediaTek chipset: Out-of-bounds Write | 6.2 | — |
| Medium | CVE-2026-20563 | MediaTek chipset: Out-of-bounds Write | 5.3 | — |
| Medium | CVE-2026-20562 | MediaTek chipset: Improper Validation of Specified Quantity in Input | 5.3 | — |
| Medium | CVE-2026-20561 | MediaTek chipset: Out-of-bounds Read | 5.3 | — |
| Medium | CVE-2026-20560 | MediaTek chipset: Out-of-bounds Read | 5.3 | — |
| High | CVE-2026-20559 | MediaTek chipset: Use After Free | 7.8 | — |
| High | CVE-2026-20558 | MediaTek chipset: Use After Free | 8.4 | — |
| High | CVE-2026-20557 | MediaTek chipset: Out-of-bounds Write | 7.5 | — |
| High | CVE-2026-20556 | MediaTek chipset: Out-of-bounds Write | 7.5 | — |
| Medium | CVE-2026-20555 | MediaTek chipset: Out-of-bounds Read | 5.3 | — |
| Medium | CVE-2026-20553 | MediaTek chipset: Out-of-bounds Write | 6.8 | — |
| High | CVE-2026-20549 | MediaTek chipset: Out-of-bounds Write | 7.5 | — |
| High | CVE-2026-20548 | MediaTek chipset: Out-of-bounds Write | 7.5 | — |
| High | CVE-2026-20547 | MediaTek chipset: Out-of-bounds Write | 7.5 | — |
| High | CVE-2026-20546 | MediaTek chipset: Out-of-bounds Write | 7.5 | — |
| High | CVE-2026-20545 | MediaTek chipset: Out-of-bounds Write | 7.5 | — |
| Medium | CVE-2026-11891 | Mali GPU Userspace Driver allows access to already freed memory | 5.1 | — |
| High | CVE-2026-0053 | Google Android: Improper Access Control | 8.4 | — |
| Medium | CVE-2025-48600 | Google Android: Missing Authorization | 5.5 | — |
| High | CVE-2025-38627 | Linux Kernel: security vulnerability | 7.8 | — |
| High | CVE-2025-26433 | Google Android: User Interface (UI) Misrepresentation of Critical Information | 8.4 | — |
| High | CVE-2025-22442 | Google Android: Race Condition | 7.0 | — |
| High | CVE-2025-22436 | Google Android: User Interface (UI) Misrepresentation of Critical Information | 8.4 | — |
| High | CVE-2025-22426 | Google Android: Improper Access Control | 7.8 | — |
| High | CVE-2025-22424 | Google Android: Improper Input Validation | 7.8 | — |
| High | CVE-2025-0647 | Arm Neoverse-N2: Sensitive Information in Resource Not Removed Before Reuse | 7.9 | — |
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-21144"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-21144.svg?lang=en" alt="CVE-2026-21144 – NEOSEC Intel" height="20"></a>