Linux Kernel up to 5.12.9 amd_sfh memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.0$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 5.12.9. Affected is an unknown function of the component amd_sfh. Performing a manipulation results in memory leak. This vulnerability is known as CVE-2021-47133. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.12.9. This affects some unknown processing of the component amd_sfh. 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: HID: amd_sfh: Fix memory leak in amd_sfh_work Kmemleak tool detected a memory leak in the amd_sfh driver. ==================== unreferenced object 0xffff88810228ada0 (size 32): comm "insmod", pid 3968, jiffies 4295056001 (age 775.792s) hex dump (first 32 bytes): 00 20 73 1f 81 88 ff ff 00 01 00 00 00 00 ad de . s............. 22 01 00 00 00 00 ad de 01 00 02 00 00 00 00 00 "............... backtrace: [] kmem_cache_alloc_trace+0x163/0x4f0 [] amd_sfh_get_report+0xa4/0x1d0 [amd_sfh] [] amdtp_hid_request+0x62/0x80 [amd_sfh] [] sensor_hub_get_feature+0x145/0x270 [hid_sensor_hub] [] hid_sensor_parse_common_attributes+0x215/0x460 [hid_sensor_iio_common] [] hid_accel_3d_probe+0xff/0x4a0 [hid_sensor_accel_3d] [] platform_probe+0x6a/0xd0 [] really_probe+0x192/0x620 [] driver_probe_device+0x14a/0x1d0 [] __device_attach_driver+0xbd/0x110 [] bus_for_each_drv+0xfd/0x160 [] __device_attach+0x18b/0x220 [] device_initial_probe+0x13/0x20 [] bus_probe_device+0xfe/0x120 [] device_add+0x6a6/0xe00 [] platform_device_add+0x180/0x380 ==================== The fix is to freeing request_list entry once the processed entry is removed from the request_list.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2021-47133 since 03/04/2024. The exploitability is told to be difficult. Neither technical details nor an exploit are publicly available.

Upgrading to version 5.12.10 or 5.13 eliminates this vulnerability. Applying the patch 29beadea66a2/5ad755fd2b32 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.

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

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.1
VulDB Meta Temp Score: 5.0

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kernel 5.12.10/5.13
Patch: 29beadea66a2/5ad755fd2b32

Timelineinfo

03/04/2024 🔍
03/15/2024 +11 days 🔍
03/15/2024 +0 days 🔍
01/07/2025 +298 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2021-47133 (🔍)
GCVE (CVE): GCVE-0-2021-47133
GCVE (VulDB): GCVE-100-257025

Entryinfo

Created: 03/15/2024 22:51
Updated: 01/07/2025 21:25
Changes: 03/15/2024 22:51 (43), 01/07/2025 21:25 (27)
Complete: 🔍
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!