CVE-2025-22124 Affecting kernel-uek-debug-modules package, versions <0:6.12.0-105.51.5.el9uek


Severity

Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.02% (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-ORACLE9-KERNELUEKDEBUGMODULES-13869085
  • published10 Nov 2025
  • disclosed16 Apr 2025

Introduced: 16 Apr 2025

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

How to fix?

Upgrade Oracle:9 kernel-uek-debug-modules to version 0:6.12.0-105.51.5.el9uek or higher.
This issue was patched in ELSA-2025-25754.

NVD Description

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

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

md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb

In clustermd, separate write-intent-bitmaps are used for each cluster node:

0 4k 8k 12k

| idle | md super | bm super [0] + bits | | bm bits[0, contd] | bm super[1] + bits | bm bits[1, contd] | | bm super[2] + bits | bm bits [2, contd] | bm super[3] + bits | | bm bits [3, contd] | | |

So in node 1, pg_index in __write_sb_page() could equal to bitmap->storage.file_pages. Then bitmap_limit will be calculated to 0. md_super_write() will be called with 0 size. That means the first 4k sb area of node 1 will never be updated through filemap_write_page(). This bug causes hang of mdadm/clustermd_tests/01r1_Grow_resize.

Here use (pg_index % bitmap->storage.file_pages) to make calculation of bitmap_limit correct.

CVSS Base Scores

version 3.1