CVE-2023-52730
published 2024-05-21CVE-2023-52730: In the Linux kernel, the following vulnerability has been resolved: mmc: sdio: fix possible resource leaks in some error paths If sdio_add_func() or…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.25%
16.5th percentile
In the Linux kernel, the following vulnerability has been resolved:
mmc: sdio: fix possible resource leaks in some error paths
If sdio_add_func() or sdio_init_func() fails, sdio_remove_func() can
not release the resources, because the sdio function is not presented
in these two cases, it won't call of_node_put() or put_device().
To fix these leaks, make sdio_func_present() only control whether
device_del() needs to be called or not, then always call of_node_put()
and put_device().
In error case in sdio_init_func(), the reference of 'card->dev' is
not get, to avoid redundant put in sdio_free_func_cis(), move the
get_device() to sdio_alloc_func() and put_device() to sdio_release_func(),
it can keep the get/put function be balanced.
Without this patch, while doing fault inject test, it can get the
following leak reports, after this fix, the leak is gone.
unreferenced object 0xffff888112514000 (size 2048):
comm "kworker/3:2", pid 65, jiffies 4294741614 (age 124.774s)
hex dump (first 32 bytes):
00 e0 6f 12 81 88 ff ff 60 58 8d 06 81 88 ff ff ..o.....`X......
10 40 51 12 81 88 ff ff 10 40 51 12 81 88 ff ff .@Q......@Q.....
backtrace:
[] kmalloc_trace+0x21/0x110
[] mmc_alloc_card+0x38/0xb0 [mmc_core]
[] mmc_sdio_init_card+0xde/0x170 [mmc_core]
[] mmc_attach_sdio+0xcb/0x1b0 [mmc_core]
[] mmc_rescan+0x54a/0x640 [mmc_core]
unreferenced object 0xffff888112511000 (size 2048):
comm "kworker/3:2", pid 65, jiffies 4294741623 (age 124.766s)
hex dump (first 32 bytes):
00 40 51 12 81 88 ff ff e0 58 8d 06 81 88 ff ff [email protected]......
10 10 51 12 81 88 ff ff 10 10 51 12 81 88 ff ff ..Q.......Q.....
backtrace:
[] kmalloc_trace+0x21/0x110
[] sdio_alloc_func+0x35/0x100 [mmc_core]
[] mmc_attach_sdio.cold.18+0xb1/0x395 [mmc_core]
[] mmc_rescan+0x54a/0x640 [mmc_core]
Affected
20 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.15-1 (bookworm) | linux 6.1.15-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 < 92ff03c2563c9b57a027c744750f3b7d2f261c58 | 92ff03c2563c9b57a027c744750f3b7d2f261c58 |
| linux | linux | >= 3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 < 5c7858adada31dbed042448cff6997dd6efc472a | 5c7858adada31dbed042448cff6997dd6efc472a |
| linux | linux | >= 3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 < 761db46b29b496946046d8cb33c7ea6de6bef36e | 761db46b29b496946046d8cb33c7ea6de6bef36e |
| linux | linux | >= 3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 < 30716d9f0fa1766e522cf24c8a456244e4fc9931 | 30716d9f0fa1766e522cf24c8a456244e4fc9931 |
| linux | linux | >= 3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 < 1e06cf04239e202248c8fa356bf11449dc73cfbd | 1e06cf04239e202248c8fa356bf11449dc73cfbd |
| linux | linux | >= 3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 < f855d31bb38d663c3ba672345d7cce9324ba3b72 | f855d31bb38d663c3ba672345d7cce9324ba3b72 |
| linux | linux | >= 3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 < 605d9fb9556f8f5fb4566f4df1480f280f308ded | 605d9fb9556f8f5fb4566f4df1480f280f308ded |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.15-1 | 6.1.15-1 |
| linux | linux_kernel | >= 0 < 6.1.15-1 | 6.1.15-1 |
| linux | linux_kernel | >= 0 < 6.1.15-1 | 6.1.15-1 |
| linux | linux_kernel | >= 2.6.33 < 4.14.306 | 4.14.306 |
| linux | linux_kernel | >= 4.15 < 4.19.273 | 4.19.273 |
| linux | linux_kernel | >= 4.20 < 5.4.232 | 5.4.232 |
| linux | linux_kernel | >= 5.11 < 5.15.95 | 5.15.95 |
| linux | linux_kernel | >= 5.16 < 6.1.13 | 6.1.13 |
| linux | linux_kernel | >= 5.5 < 5.10.169 | 5.10.169 |
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-64v3-vwp6-q2hj: In the Linux kernel, the following vulnerability has been resolved:
mmc: sdio: fix possible resource leaks in some error paths
If sdio_add_func() or
ghsa_unreviewed·2024-05-21
CVE-2023-52730 [MEDIUM] CWE-401 GHSA-64v3-vwp6-q2hj: In the Linux kernel, the following vulnerability has been resolved:
mmc: sdio: fix possible resource leaks in some error paths
If sdio_add_func() or
In the Linux kernel, the following vulnerability has been resolved:
mmc: sdio: fix possible resource leaks in some error paths
If sdio_add_func() or sdio_init_func() fails, sdio_remove_func() can
not release the resources, because the sdio function is not presented
in these two cases, it won't call of_node_put() or put_device().
To fix these leaks, make sdio_func_present() only control whether
device_del() needs to be called or not, then always call of_node_put()
and put_device().
In error case in sdio_init_func(), the reference of 'card->dev' is
not get, to avoid redundant put in sdio_free_func_cis(), move the
get_device() to sdio_alloc_func() and put_device() to sdio_release_func(),
it can keep the get/put function be balanced.
Without this patch, while doing fault inject test, it c
OSV
CVE-2023-52730: In the Linux kernel, the following vulnerability has been resolved: mmc: sdio: fix possible resource leaks in some error paths If sdio_add_func() or s
osv·2024-05-21·CVSS 5.5
CVE-2023-52730 [MEDIUM] CVE-2023-52730: In the Linux kernel, the following vulnerability has been resolved: mmc: sdio: fix possible resource leaks in some error paths If sdio_add_func() or s
In the Linux kernel, the following vulnerability has been resolved: mmc: sdio: fix possible resource leaks in some error paths If sdio_add_func() or sdio_init_func() fails, sdio_remove_func() can not release the resources, because the sdio function is not presented in these two cases, it won't call of_node_put() or put_device(). To fix these leaks, make sdio_func_present() only control whether device_del() needs to be called or not, then always call of_node_put() and put_device(). In error case in sdio_init_func(), the reference of 'card->dev' is not get, to avoid redundant put in sdio_free_func_cis(), move the get_device() to sdio_alloc_func() and put_device() to sdio_release_func(), it can keep the get/put function be balanced. Without this patch, while doing fault inject test, it can ge
Red Hat
kernel: mmc: sdio: fix possible resource leaks in some error paths
vendor_redhat·2024-05-21·CVSS 5.5
CVE-2023-52730 [MEDIUM] CWE-402 kernel: mmc: sdio: fix possible resource leaks in some error paths
kernel: mmc: sdio: fix possible resource leaks in some error paths
In the Linux kernel, the following vulnerability has been resolved:
mmc: sdio: fix possible resource leaks in some error paths
If sdio_add_func() or sdio_init_func() fails, sdio_remove_func() can
not release the resources, because the sdio function is not presented
in these two cases, it won't call of_node_put() or put_device().
To fix these leaks, make sdio_func_present() only control whether
device_del() needs to be called or not, then always call of_node_put()
and put_device().
In error case in sdio_init_func(), the reference of 'card->dev' is
not get, to avoid redundant put in sdio_free_func_cis(), move the
get_device() to sdio_alloc_func() and put_device() to sdio_release_func(),
it can keep the get/put function be ba
Debian
CVE-2023-52730: linux - In the Linux kernel, the following vulnerability has been resolved: mmc: sdio: ...
vendor_debian·2023·CVSS 5.5
CVE-2023-52730 [MEDIUM] CVE-2023-52730: linux - In the Linux kernel, the following vulnerability has been resolved: mmc: sdio: ...
In the Linux kernel, the following vulnerability has been resolved: mmc: sdio: fix possible resource leaks in some error paths If sdio_add_func() or sdio_init_func() fails, sdio_remove_func() can not release the resources, because the sdio function is not presented in these two cases, it won't call of_node_put() or put_device(). To fix these leaks, make sdio_func_present() only control whether device_del() needs to be called or not, then always call of_node_put() and put_device(). In error case in sdio_init_func(), the reference of 'card->dev' is not get, to avoid redundant put in sdio_free_func_cis(), move the get_device() to sdio_alloc_func() and put_device() to sdio_release_func(), it can keep the get/put function be balanced. Without this patch, while doing fault inject test, it can ge
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/1e06cf04239e202248c8fa356bf11449dc73cfbdhttps://git.kernel.org/stable/c/30716d9f0fa1766e522cf24c8a456244e4fc9931https://git.kernel.org/stable/c/5c7858adada31dbed042448cff6997dd6efc472ahttps://git.kernel.org/stable/c/605d9fb9556f8f5fb4566f4df1480f280f308dedhttps://git.kernel.org/stable/c/761db46b29b496946046d8cb33c7ea6de6bef36ehttps://git.kernel.org/stable/c/92ff03c2563c9b57a027c744750f3b7d2f261c58https://git.kernel.org/stable/c/f855d31bb38d663c3ba672345d7cce9324ba3b72https://git.kernel.org/stable/c/1e06cf04239e202248c8fa356bf11449dc73cfbdhttps://git.kernel.org/stable/c/30716d9f0fa1766e522cf24c8a456244e4fc9931https://git.kernel.org/stable/c/5c7858adada31dbed042448cff6997dd6efc472ahttps://git.kernel.org/stable/c/605d9fb9556f8f5fb4566f4df1480f280f308dedhttps://git.kernel.org/stable/c/761db46b29b496946046d8cb33c7ea6de6bef36ehttps://git.kernel.org/stable/c/92ff03c2563c9b57a027c744750f3b7d2f261c58https://git.kernel.org/stable/c/f855d31bb38d663c3ba672345d7cce9324ba3b72
2024-05-21
Published