CVE-2025-38352 Affecting bpftool package, versions <0:4.18.0-553.74.1.el8_10


Severity

Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

Exploit Maturity
Attacked
EPSS
4.24% (89th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ORACLE8-BPFTOOL-12566410
  • published9 Sept 2025
  • disclosed22 Jul 2025

Introduced: 22 Jul 2025

CVE-2025-38352  (opens in a new tab)

How to fix?

Upgrade Oracle:8 bpftool to version 0:4.18.0-553.74.1.el8_10 or higher.
This issue was patched in ELSA-2025-15471.

NVD Description

Note: Versions mentioned in the description apply only to the upstream bpftool package and not the bpftool package as distributed by Oracle. See How to fix? for Oracle:8 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()

If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand().

If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail.

Add the tsk->exit_state check into run_posix_cpu_timers() to fix this.

This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.

CVSS Base Scores

version 3.1