Linux Kernel up to 5.10.157/5.15.81/6.0.11 raydium_i2c_send memory leak

Summaryinfo

A vulnerability was found in Linux Kernel up to 5.10.157/5.15.81/6.0.11. It has been declared as critical. This affects the function raydium_i2c_send. The manipulation results in memory leak. This vulnerability is reported as CVE-2022-48995. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 5.10.157/5.15.81/6.0.11. Affected is the function raydium_i2c_send. 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. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: Input: raydium_ts_i2c - fix memory leak in raydium_i2c_send() There is a kmemleak when test the raydium_i2c_ts with bpf mock device: unreferenced object 0xffff88812d3675a0 (size 8): comm "python3", pid 349, jiffies 4294741067 (age 95.695s) hex dump (first 8 bytes): 11 0e 10 c0 01 00 04 00 ........ backtrace: [] __kmalloc+0x46/0x1b0 [] raydium_i2c_send+0xd4/0x2bf [raydium_i2c_ts] [] raydium_i2c_initialize.cold+0xbc/0x3e4 [raydium_i2c_ts] [] raydium_i2c_probe+0x3cd/0x6bc [raydium_i2c_ts] [] i2c_device_probe+0x651/0x680 [] really_probe+0x17c/0x3f0 [] __driver_probe_device+0xe3/0x170 [] driver_probe_device+0x49/0x120 [] __device_attach_driver+0xf7/0x150 [] bus_for_each_drv+0x114/0x180 [] __device_attach+0x1e5/0x2d0 [] bus_probe_device+0x126/0x140 [] device_add+0x810/0x1130 [] i2c_new_client_device+0x352/0x4e0 [] of_i2c_register_device+0xf1/0x110 [] of_i2c_notify+0x100/0x160 unreferenced object 0xffff88812d3675c8 (size 8): comm "python3", pid 349, jiffies 4294741070 (age 95.692s) hex dump (first 8 bytes): 22 00 36 2d 81 88 ff ff ".6-.... backtrace: [] __kmalloc+0x46/0x1b0 [] raydium_i2c_send+0xd4/0x2bf [raydium_i2c_ts] [] raydium_i2c_initialize.cold+0x223/0x3e4 [raydium_i2c_ts] [] raydium_i2c_probe+0x3cd/0x6bc [raydium_i2c_ts] [] i2c_device_probe+0x651/0x680 [] really_probe+0x17c/0x3f0 [] __driver_probe_device+0xe3/0x170 [] driver_probe_device+0x49/0x120 [] __device_attach_driver+0xf7/0x150 [] bus_for_each_drv+0x114/0x180 [] __device_attach+0x1e5/0x2d0 [] bus_probe_device+0x126/0x140 [] device_add+0x810/0x1130 [] i2c_new_client_device+0x352/0x4e0 [] of_i2c_register_device+0xf1/0x110 [] of_i2c_notify+0x100/0x160 After BANK_SWITCH command from i2c BUS, no matter success or error happened, the tx_buf should be freed.

The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2022-48995 since 08/22/2024. The exploitability is told to be difficult. Technical details are known, but there is no available exploit.

Upgrading to version 5.10.158, 5.15.82 or 6.0.12 eliminates this vulnerability. Applying the patch a82869ac52f3/53b9b1201e34/097c1c7a28e3/8c9a59939deb 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 CERT Bund (WID-SEC-2024-3251). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

• Google Container-Optimized OS
• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• NetApp StorageGRID
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• Kyocera Printer
• NetApp AFF
• NetApp ActiveIQ Unified Manager
• SUSE openSUSE
• IBM Security Guardium
• RESF Rocky Linux
• Dell NetWorker
• Dell Avamar
• IBM QRadar SIEM
• NetApp FAS
• SolarWinds Security Event Manager
• Dell PowerProtect Data Domain
• Open Source Linux Kernel
• Dell PowerScale OneFS

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.10.157
• 5.15.0
• 5.15.1
• 5.15.2
• 5.15.3
• 5.15.4
• 5.15.5
• 5.15.6
• 5.15.7
• 5.15.8
• 5.15.9
• 5.15.10
• 5.15.11
• 5.15.12
• 5.15.13
• 5.15.14
• 5.15.15
• 5.15.16
• 5.15.17
• 5.15.18
• 5.15.19
• 5.15.20
• 5.15.21
• 5.15.22
• 5.15.23
• 5.15.24
• 5.15.25
• 5.15.26
• 5.15.27
• 5.15.28
• 5.15.29
• 5.15.30
• 5.15.31
• 5.15.32
• 5.15.33
• 5.15.34
• 5.15.35
• 5.15.36
• 5.15.37
• 5.15.38
• 5.15.39
• 5.15.40
• 5.15.41
• 5.15.42
• 5.15.43
• 5.15.44
• 5.15.45
• 5.15.46
• 5.15.47
• 5.15.48
• 5.15.49
• 5.15.50
• 5.15.51
• 5.15.52
• 5.15.53
• 5.15.54
• 5.15.55
• 5.15.56
• 5.15.57
• 5.15.58
• 5.15.59
• 5.15.60
• 5.15.61
• 5.15.62
• 5.15.63
• 5.15.64
• 5.15.65
• 5.15.66
• 5.15.67
• 5.15.68
• 5.15.69
• 5.15.70
• 5.15.71
• 5.15.72
• 5.15.73
• 5.15.74
• 5.15.75
• 5.15.76
• 5.15.77
• 5.15.78
• 5.15.79
• 5.15.80
• 5.15.81
• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7
• 6.0.8
• 6.0.9
• 6.0.10
• 6.0.11

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

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion