CVE-2026-98953 Affecting kernel6.12-devel package, versions <1:6.12.113-138.209.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 applications- Snyk IDSNYK-AMZN2023-KERNEL612DEVEL-21812066
- published29 Oct 2026
- disclosed23 Oct 2026
Introduced: 23 Oct 2026
NewCVE-2026-98953 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 kernel6.12-devel to version 1:6.12.113-138.209.amzn2023 or higher.
This issue was patched in ALAS2023-2026-3335.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel6.12-devel package and not the kernel6.12-devel 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:
devlink: fix devlink_rel reference leak when notify work is pending
devlink_rel_nested_in_notify_work_schedule() takes a reference on the devlink_rel for the notify work and then queues the work, ignoring the return value of schedule_delayed_work(). If the work is already pending, nothing new is queued, the work runs only once and drops only one reference, so the extra one is leaked together with the devlink_rel and its index in devlink_rels.
This is easy to hit. devl_register() of a nested instance queues the work, and if the instance is unregistered before the work has run, devlink_rel_put() queues it again while it is still pending. The work also keeps rescheduling itself for as long as the parent devlink lock cannot be taken, which widens the window. Registering and unregistering a nested devlink instance 100 times while holding the parent lock leaks all 100 devlink_rel objects.
The reschedule path in devlink_rel_nested_in_notify_work() has the same problem: if the work was queued again while it was running, the reference it holds is never dropped.
Drop the reference in both places when the work was already pending. The pending work holds its own reference, so this can not be the last one.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-98953
- https://git.kernel.org/stable/c/8c7830e0120e6e1f5084212fd5b79b3092496f87
- https://git.kernel.org/stable/c/8de57bfec3825effb57fe4d25da98ec3b8fda4c6
- https://git.kernel.org/stable/c/c5381ae1cd1481cc431c2bd79460472c6f1d3ce3
- https://git.kernel.org/stable/c/dc2e787b5fb474241c8a6d18fdacb44adc6d571f