CVE-2024-50201 Affecting kernel-rt-modules-partner package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise 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-RHEL9-KERNELRTMODULESPARTNER-8429514
  • published27 Nov 2024
  • disclosed8 Nov 2024

Introduced: 8 Nov 2024

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

How to fix?

There is no fixed version for RHEL:9 kernel-rt-modules-partner.

NVD Description

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

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

drm/radeon: Fix encoder->possible_clones

Include the encoder itself in its possible_clones bitmask. In the past nothing validated that drivers were populating possible_clones correctly, but that changed in commit 74d2aacbe840 ("drm: Validate encoder->possible_clones"). Looks like radeon never got the memo and is still not following the rules 100% correctly.

This results in some warnings during driver initialization: Bogus possible_clones: [ENCODER:46:TV-46] possible_clones=0x4 (full encoder mask=0x7) WARNING: CPU: 0 PID: 170 at drivers/gpu/drm/drm_mode_config.c:615 drm_mode_config_validate+0x113/0x39c ...

(cherry picked from commit 3b6e7d40649c0d75572039aff9d0911864c689db)

CVSS Scores

version 3.1