CVE-2024-50023 Affecting kernel-cross-headers 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-KERNELCROSSHEADERS-8259866
  • published23 Oct 2024
  • disclosed21 Oct 2024

Introduced: 21 Oct 2024

CVE-2024-50023  (opens in a new tab)
First added by Snyk

How to fix?

There is no fixed version for RHEL:9 kernel-cross-headers.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-cross-headers package and not the kernel-cross-headers 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:

net: phy: Remove LED entry from LEDs list on unregister

Commit c938ab4da0eb ("net: phy: Manual remove LEDs to ensure correct ordering") correctly fixed a problem with using devm_ but missed removing the LED entry from the LEDs list.

This cause kernel panic on specific scenario where the port for the PHY is torn down and up and the kmod for the PHY is removed.

On setting the port down the first time, the assosiacted LEDs are correctly unregistered. The associated kmod for the PHY is now removed. The kmod is now added again and the port is now put up, the associated LED are registered again. On putting the port down again for the second time after these step, the LED list now have 4 elements. With the first 2 already unregistered previously and the 2 new one registered again.

This cause a kernel panic as the first 2 element should have been removed.

Fix this by correctly removing the element when LED is unregistered.

CVSS Scores

version 3.1