CVSS 3.1
8.1 highCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:HHigh (8.1) in samsung semiconductor. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:HExplain CVE-2026-68984 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-68984?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-68984?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-68984 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Samsung Semiconductor Exynos 2100 | before November 2026 |
| Samsung Semiconductor Exynos 1280 | before November 2026 |
| Samsung Semiconductor Exynos 2200 | before November 2026 |
| Samsung Semiconductor Exynos 1380 | before November 2026 |
| Samsung Semiconductor Exynos 1480 | before November 2026 |
| Samsung Semiconductor Exynos 2400 | before November 2026 |
| Samsung Semiconductor Exynos 1580 | before November 2026 |
| Samsung Semiconductor Exynos 2500 | before November 2026 |
| Samsung Semiconductor Exynos 2600 | before November 2026 |
| Samsung Semiconductor Exynos 1680 | before November 2026 |
Red Hat rates this Important.
This vulnerability is rated as having an Important impact because a local, unprivileged user could induce kernel memory corruption, potentially leading to privilege escalation or a denial of service. However, exploitation requires underlying Samsung Exynos system-on-chip hardware. Red Hat Enterprise Linux does not include or support drivers for this hardware platform, so supported Red Hat configurations are not exposed.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
--- CME Mitigation Guidance (2026-11-06) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to trap integer wraparounds before corrupted sizes reach allocation or copying logic in the Samsung Exynos NPU kernel driver: upgrade to the corresponding fixed Red Hat builds, which vendor patch details are not specified in the advisory, closing crafted driver invocation triggering integer overflow. Until patched, this is only a concern on Linux systems on affected Samsung Exynos SoCs with local unprivileged code execution — Red Hat Enterprise Linux and hardware lacking Samsung Exynos SoCs are unaffected — so Restrict local unprivileged user access to the Samsung Exynos NPU driver device node and limit local unprivileged execution. As a compensating measure, Enable runtime memory error detection with KASAN or HWASan to catch out-of-bounds access and heap corruption, Enable KASLR to randomize kernel base addresses and obstruct code reuse attacks, Enable SMEP to block the kernel from executing code in userspace memory, Enable SMAP to prevent direct kernel access to userspace memory during driver calls, Enforce kernel forward and backward edge Control Flow Integrity to prevent control-flow hijacking via corrupted function pointers, and Enable SLAB freelist hardening and randomization to prevent freelist corruption and heap metadata tampering. These controls limit blast radius and contain exploitation, but they do not fix the underlying integer overflow defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Affected | |
| Red Hat Enterprise Linux 10 | libkrun | Affected | |
| Red Hat Enterprise Linux 6 | kernel | Affected | |
| Red Hat Enterprise Linux 7 | kernel | Affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Affected | |
| Red Hat Enterprise Linux 8 | kernel | Affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Affected | |
| Red Hat Enterprise Linux 9 | kernel | Affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-68984.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
Changes since this site first stored the record. The same for every record: /api/public/changes.