Linux Kernel up to 6.10.4 bcm_sf2_mdio_register memory leak

Summaryinfo

A vulnerability identified as critical has been detected in Linux Kernel up to 5.10.223/5.15.164/6.1.104/6.6.45/6.10.4. This affects the function bcm_sf2_mdio_register. Performing a manipulation results in memory leak. This vulnerability is reported as CVE-2024-44971. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.10.223/5.15.164/6.1.104/6.6.45/6.10.4. This affects the function bcm_sf2_mdio_register. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() bcm_sf2_mdio_register() calls of_phy_find_device() and then phy_device_remove() in a loop to remove existing PHY devices. of_phy_find_device() eventually calls bus_find_device(), which calls get_device() on the returned struct device * to increment the refcount. The current implementation does not decrement the refcount, which causes memory leak. This commit adds the missing phy_device_free() call to decrement the refcount via put_device() to balance the refcount.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2024-44971 since 08/21/2024. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 208425 (SUSE SLES15 Security Update : kernel (SUSE-SU-2024:3553-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.224, 5.15.165, 6.1.105, 6.6.46 or 6.10.5 eliminates this vulnerability. Applying the patch b7b8d9f5e679/c05516c07290/7feef10768ea/a7d2808d6757/f3d5efe18a11/e3862093ee93 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (208425). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.10.223
• 5.15.164
• 6.1.104
• 6.6.0
• 6.6.1
• 6.6.2
• 6.6.3
• 6.6.4
• 6.6.5
• 6.6.6
• 6.6.7
• 6.6.8
• 6.6.9
• 6.6.10
• 6.6.11
• 6.6.12
• 6.6.13
• 6.6.14
• 6.6.15
• 6.6.16
• 6.6.17
• 6.6.18
• 6.6.19
• 6.6.20
• 6.6.21
• 6.6.22
• 6.6.23
• 6.6.24
• 6.6.25
• 6.6.26
• 6.6.27
• 6.6.28
• 6.6.29
• 6.6.30
• 6.6.31
• 6.6.32
• 6.6.33
• 6.6.34
• 6.6.35
• 6.6.36
• 6.6.37
• 6.6.38
• 6.6.39
• 6.6.40
• 6.6.41
• 6.6.42
• 6.6.43
• 6.6.44
• 6.6.45
• 6.10.0
• 6.10.1
• 6.10.2
• 6.10.3
• 6.10.4

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion