CVE-2026-21996

An unprivileged attacker can reliably trigger a crash of the dtrace process with a malicious ELF binary due to an integer Divide-by-Zero in Pbuild_file_symtab()

Published: 2026-05-01 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-21996 is rated Low Risk (13.8/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.11%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-21996

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.11% +0.10%
2 2026-05-02 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-21996

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.8 1.4 [email protected]
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2026-21996

GitHub Security Advisory for CVE-2026-21996

GHSA-w2v2-5qjc-q2jw · Severity: low — An unprivileged attacker can reliably trigger a crash of the dtrace process with a malicious ELF...

OS Trackers for CVE-2026-21996

vendor priority summary link
debian not yet assigned CVE-2026-21996 not yet assigned priority: Debian including 1 source packages (dtrace), 1 status rows across 1 suites (sid): resolved 1. https://security-tracker.debian.org/tracker/CVE-2026-21996
ubuntu medium CVE-2026-21996 medium priority: Ubuntu including 1 source packages (dtrace), 5 status rows across 5 suites (jammy, noble, questing, resolute, upstream): DNE 3, needs-triage 2. https://ubuntu.com/security/CVE-2026-21996

Affected software / configurations for CVE-2026-21996

Vendor Product Version Raw CPE
oracle linux 8 cpe:2.3:o:oracle:linux:8:-:*:*:*:*:*:*
oracle linux 9 cpe:2.3:o:oracle:linux:9:0:*:*:*:*:*:*
oracle linux 10 cpe:2.3:o:oracle:linux:10:0:*:*:*:*:*:*

References for CVE-2026-21996

cvelogic Threat Intelligence