CVE-2025-39870 Affecting kernel-uek64k-modules-usb package, versions <0:6.12.0-105.51.5.el10uek


Severity

Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.04% (11th 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-ORACLE10-KERNELUEK64KMODULESUSB-13870084
  • published10 Nov 2025
  • disclosed23 Sept 2025

Introduced: 23 Sep 2025

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

How to fix?

Upgrade Oracle:10 kernel-uek64k-modules-usb to version 0:6.12.0-105.51.5.el10uek or higher.
This issue was patched in ELSA-2025-25754.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-uek64k-modules-usb package and not the kernel-uek64k-modules-usb package as distributed by Oracle. See How to fix? for Oracle:10 relevant fixed versions and status.

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

dmaengine: idxd: Fix double free in idxd_setup_wqs()

The clean up in idxd_setup_wqs() has had a couple bugs because the error handling is a bit subtle. It's simpler to just re-write it in a cleaner way. The issues here are:

  1. If "idxd->max_wqs" is <= 0 then we call put_device(conf_dev) when "conf_dev" hasn't been initialized.
  2. If kzalloc_node() fails then again "conf_dev" is invalid. It's either uninitialized or it points to the "conf_dev" from the previous iteration so it leads to a double free.

It's better to free partial loop iterations within the loop and then the unwinding at the end can handle whole loop iterations. I also renamed the labels to describe what the goto does and not where the goto was located.

CVSS Base Scores

version 3.1