NULL Pointer Dereference Affecting perf-debuginfo package, versions <1:6.1.159-181.297.amzn2023
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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 applicationsSnyk Learn
Learn about NULL Pointer Dereference vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-AMZN2023-PERFDEBUGINFO-14905464
- published9 Jan 2026
- disclosed16 Dec 2025
Introduced: 16 Dec 2025
CVE-2025-68214 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 perf-debuginfo to version 1:6.1.159-181.297.amzn2023 or higher.
This issue was patched in ALAS2023-2025-1350.
NVD Description
Note: Versions mentioned in the description apply only to the upstream perf-debuginfo package and not the perf-debuginfo package as distributed by Amazon-Linux.
See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
timers: Fix NULL function pointer race in timer_shutdown_sync()
There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers().
The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this:
CPU0 CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now timer is pending while its function set to NULL. // next timer trigger <SOFTIRQ> expire_timers() WARN_ON_ONCE(!fn) // hit ... lock_timer_base() // Now timer will detach if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base()
The problem is that timer_shutdown_sync() clears the timer function regardless of whether the timer is currently running. This can leave a pending timer with a NULL function pointer, which triggers the WARN_ON_ONCE(!fn) check in expire_timers().
Fix this by only clearing the timer function when actually detaching the timer. If the timer is running, leave the function pointer intact, which is safe because the timer will be properly detached when it finishes running.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-68214
- https://git.kernel.org/stable/c/176725f4848376530a0f0da9023f956afcc33585
- https://git.kernel.org/stable/c/1a975716cc8977f461e45e28e3e5977d46ad7a6a
- https://git.kernel.org/stable/c/20739af07383e6eb1ec59dcd70b72ebfa9ac362c
- https://git.kernel.org/stable/c/6665fbd7730b26d770c232b20d1b907e6a67a914
- https://git.kernel.org/stable/c/a01efa7a780c42ac5170a949bd95c9786ffcc60a
- https://git.kernel.org/stable/c/ba43ac025c4318241f8edf94f31d2eebab86991b