Описание
ELSA-2026-50250: dtrace security update (MODERATE)
[2.0.7-4]
- Prevent out-of-buonds memory access during object symbol table construction (CVE-2026-35233). [Orabug: 39121881]
- Prevent divide-by-zero (FPE trap) if section header data is corrupted. (CVE-2026-21996). [Orabug: 39121874]
- Ensure safety checks are performed on program header data from ELF objects.
- Ensure that the data of string table sections is proper terminated.
- Ensure that the symbol table references a valid string table.
Credit Statement: The following people or organizations reported security vulnerabilities addressed by this ELSA to Oracle: Vishal Panchani CVE-2026-35233 CVE-2026-21996
Обновленные пакеты
Oracle Linux 8
Oracle Linux aarch64
dtrace
2.0.7-4.el8
dtrace-devel
2.0.7-4.el8
dtrace-testsuite
2.0.7-4.el8
Oracle Linux x86_64
dtrace
2.0.7-4.el8
dtrace-devel
2.0.7-4.el8
dtrace-testsuite
2.0.7-4.el8
Oracle Linux 9
Oracle Linux aarch64
dtrace
2.0.7-4.el9
dtrace-devel
2.0.7-4.el9
dtrace-testsuite
2.0.7-4.el9
Oracle Linux x86_64
dtrace
2.0.7-4.el9
dtrace-devel
2.0.7-4.el9
dtrace-testsuite
2.0.7-4.el9
Связанные CVE
Связанные уязвимости
An unprivileged attacker can craft a user-space process with a malicious ELF binary containing an out-of-range sh_link field. When root-level dtrace attaches to -- or instruments -- that process (via dtrace -p , pid probes, or USDT), the ELF parser reads heap memory beyond the allocated section cache array without any bounds check. This results in an uninitialized/out-of-bounds heap read that can cause a NULL pointer dereference crash of the dtrace process (DoS), or -- depending on heap layout -- a read-then-use of a garbage pointer controlled by adjacent allocations, providing a foothold toward further exploitation in a privileged context.
An unprivileged attacker can craft a user-space process with a malicious ELF binary containing an out-of-range sh_link field. When root-level dtrace attaches to -- or instruments -- that process (via dtrace -p , pid probes, or USDT), the ELF parser reads heap memory beyond the allocated section cache array without any bounds check. This results in an uninitialized/out-of-bounds heap read that can cause a NULL pointer dereference crash of the dtrace process (DoS), or -- depending on heap layout -- a read-then-use of a garbage pointer controlled by adjacent allocations, providing a foothold toward further exploitation in a privileged context.
An unprivileged attacker can craft a user-space process with a malicio ...