There is no fixed version for Centos:9 kernel-64k-debug-modules-internal .

NVD Description

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

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

perf/core: Order the PMU list to fix warning about unordered pmu_ctx_list

Syskaller triggers a warning due to prev_epc->pmu != next_epc->pmu in perf_event_swap_task_ctx_data(). vmcore shows that two lists have the same perf_event_pmu_context, but not in the same order.

The problem is that the order of pmu_ctx_list for the parent is impacted by the time when an event/PMU is added. While the order for a child is impacted by the event order in the pinned_groups and flexible_groups. So the order of pmu_ctx_list in the parent and child may be different.

To fix this problem, insert the perf_event_pmu_context to its proper place after iteration of the pmu_ctx_list.

The follow testcase can trigger above warning:

perf record -e cycles --call-graph lbr -- taskset -c 3 ./a.out &

perf stat -e cpu-clock,cs -p xxx // xxx is the pid of a.out

test.c

void main() { int count = 0; pid_t pid;

    printf(&#34;%d running\n&#34;, getpid());
    sleep(30);
    printf(&#34;running\n&#34;);

pid = fork();
if (pid == -1) {
        printf(&amp;#34;fork error\n&amp;#34;);
        return;
}
if (pid == 0) {
        while (1) {
                count++;
        }
} else {
        while (1) {
                count++;
        }
}

}

The testcase first opens an LBR event, so it will allocate task_ctx_data, and then open tracepoint and software events, so the parent context will have 3 different perf_event_pmu_contexts. On inheritance, child ctx will insert the perf_event_pmu_context in another order and the warning will trigger.

[ mingo: Tidied up the changelog. ]

CVE-2025-21895 Affecting kernel-64k-debug-modules-internal package, versions *

Severity

Do your applications use this vulnerable package?

Introduced: 1 Apr 2025

How to fix?

NVD Description

perf record -e cycles --call-graph lbr -- taskset -c 3 ./a.out &

perf stat -e cpu-clock,cs -p xxx // xxx is the pid of a.out

References

CVSS Base Scores

Red Hat