CVE-2022-48995
published 2024-10-21CVE-2022-48995: 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…
PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
14.4th percentile
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.
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.12-1 (bookworm) | linux 6.0.12-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 3b384bd6c3f2d6d3526c77bfb264dfbaf737bc2a < a82869ac52f3d9db4b2cf8fd41edc2dee7a75a61 | a82869ac52f3d9db4b2cf8fd41edc2dee7a75a61 |
| linux | linux | >= 3b384bd6c3f2d6d3526c77bfb264dfbaf737bc2a < 53b9b1201e34ccc895971218559123625c56fbcd | 53b9b1201e34ccc895971218559123625c56fbcd |
| linux | linux | >= 3b384bd6c3f2d6d3526c77bfb264dfbaf737bc2a < 097c1c7a28e3da8f2811ba532be6e81faab15aab | 097c1c7a28e3da8f2811ba532be6e81faab15aab |
| linux | linux | >= 3b384bd6c3f2d6d3526c77bfb264dfbaf737bc2a < 8c9a59939deb4bfafdc451100c03d1e848b4169b | 8c9a59939deb4bfafdc451100c03d1e848b4169b |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.158-1 | 5.10.158-1 |
| linux | linux_kernel | >= 0 < 6.0.12-1 | 6.0.12-1 |
| linux | linux_kernel | >= 0 < 6.0.12-1 | 6.0.12-1 |
| linux | linux_kernel | >= 0 < 6.0.12-1 | 6.0.12-1 |
| linux | linux_kernel | >= 5.10 < 5.10.158 | 5.10.158 |
| linux | linux_kernel | >= 5.11 < 5.15.82 | 5.15.82 |
| linux | linux_kernel | >= 5.16 < 6.0.12 | 6.0.12 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-3xrg-jvxh-2hpf: In the Linux kernel, the following vulnerability has been resolved:
Input: raydium_ts_i2c - fix memory leak in raydium_i2c_send()
There is a kmemlea
ghsa_unreviewed·2024-10-21
CVE-2022-48995 [MEDIUM] CWE-401 GHSA-3xrg-jvxh-2hpf: In the Linux kernel, the following vulnerability has been resolved:
Input: raydium_ts_i2c - fix memory leak in raydium_i2c_send()
There is a kmemlea
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_p
OSV
CVE-2022-48995: 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
osv·2024-10-21·CVSS 5.5
CVE-2022-48995 [MEDIUM] CVE-2022-48995: 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
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_prob
Red Hat
kernel: Input: raydium_ts_i2c - fix memory leak in raydium_i2c_send()
vendor_redhat·2024-10-21·CVSS 5.5
CVE-2022-48995 [MEDIUM] CWE-401 kernel: Input: raydium_ts_i2c - fix memory leak in raydium_i2c_send()
kernel: Input: raydium_ts_i2c - fix memory leak in raydium_i2c_send()
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
[]
Debian
CVE-2022-48995: linux - In the Linux kernel, the following vulnerability has been resolved: Input: rayd...
vendor_debian·2022·CVSS 5.5
CVE-2022-48995 [MEDIUM] CVE-2022-48995: linux - In the Linux kernel, the following vulnerability has been resolved: Input: rayd...
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_prob
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-10-21
Published