CVE-2024-44968 Affecting kernel-uek-core package, versions <0:5.15.0-302.167.6.el8uek


Severity

Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.04% (6th 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-ORACLE8-KERNELUEKCORE-8372516
  • published14 Nov 2024
  • disclosed4 Sept 2024

Introduced: 4 Sep 2024

CVE-2024-44968  (opens in a new tab)

How to fix?

Upgrade Oracle:8 kernel-uek-core to version 0:5.15.0-302.167.6.el8uek or higher.
This issue was patched in ELSA-2024-12815.

NVD Description

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

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

tick/broadcast: Move per CPU pointer access into the atomic section

The recent fix for making the take over of the broadcast timer more reliable retrieves a per CPU pointer in preemptible context.

This went unnoticed as compilers hoist the access into the non-preemptible region where the pointer is actually used. But of course it's valid that the compiler keeps it at the place where the code puts it which rightfully triggers:

BUG: using smp_processor_id() in preemptible [00000000] code: caller is hotplug_cpu__broadcast_tick_pull+0x1c/0xc0

Move it to the actual usage site which is in a non-preemptible region.

CVSS Scores

version 3.1