Reachable Assertion Affecting kernel-uek-debug-modules-core package, versions <0:6.12.0-205.92.4.2.el10uek


Severity

Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.12% (3rd 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-KERNELUEKDEBUGMODULESCORE-18604922
  • published10 Aug 2026
  • disclosed11 Sept 2025

Introduced: 11 Sep 2025

CVE-2025-39768  (opens in a new tab)
CWE-617  (opens in a new tab)

How to fix?

Upgrade Oracle:10 kernel-uek-debug-modules-core to version 0:6.12.0-205.92.4.2.el10uek or higher.
This issue was patched in ELSA-2026-500150.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-uek-debug-modules-core package and not the kernel-uek-debug-modules-core 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:

net/mlx5: HWS, fix complex rules rehash error flow

Moving rules from matcher to matcher should not fail. However, if it does fail due to various reasons, the error flow should allow the kernel to continue functioning (albeit with broken steering rules) instead of going into series of soft lock-ups or some other problematic behaviour.

Similar to the simple rules, complex rules rehash logic suffers from the same problems. This patch fixes the error flow for moving complex rules:

  • If new rule creation fails before it was even enqeued, do not poll for completion
  • If TIMEOUT happened while moving the rule, no point trying to poll for completions for other rules. Something is broken, completion won't come, just abort the rehash sequence.
  • If some other completion with error received, don't give up. Continue handling rest of the rules to minimize the damage.
  • Make sure that the first error code that was received will be actually returned to the caller instead of replacing it with the generic error code.

All the aforementioned issues stem from the same bad error flow, so no point fixing them one by one and leaving partially broken code - fixing them in one patch.

CVSS Base Scores

version 3.1