CVE-2023-52730
mmc: sdio: fix possible resource leaks in some error paths
Reported by linux · Published May 21, 2024
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: [<000000009e5931da>] kmalloc_trace+0x21/0x110 [<000000002f839ccb>] mmc_alloc_card+0x38/0xb0 [mmc_core] [<0000000004adcbf6>] mmc_sdio_init_card+0xde/0x170 [mmc_core] [<000000007538fea0>] mmc_attach_sdio+0xcb/0x1b0 [mmc_core] [<00000000d4fdeba7>] 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 .@Q......X...... 10 10 51 12 81 88 ff ff 10 10 51 12 81 88 ff ff ..Q.......Q..... backtrace: [<000000009e5931da>] kmalloc_trace+0x21/0x110 [<00000000fcbe706c>] sdio_alloc_func+0x35/0x100 [mmc_core] [<00000000c68f4b50>] mmc_attach_sdio.cold.18+0xb1/0x395 [mmc_core] [<00000000d4fdeba7>] mmc_rescan+0x54a/0x640 [mmc_core]
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-devel | Amazon Linux | 4.14.309-231.529.amzn2 |
| kernel-headers | Amazon Linux | 4.14.309-231.529.amzn2 |
| kernel-tools | Amazon Linux | 4.14.309-231.529.amzn2 |
| perf | Amazon Linux | 4.14.309-231.529.amzn2 |
| kernel-livepatch-4.14.309-231.529 | Amazon Linux | 1.0-0.amzn2 |
| linux_kernel | linux | 6.1.13, 5.15.95, 5.10.169, 5.4.232, 4.19.273, 4.14.306 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5, 3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5, 3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 |
| Linux | Linux | 2.6.33, 0, 4.14.306 |
| amazon:2 | kernel-devel | 0 |
| amazon:2 | kernel-headers | 0 |
| amazon:2 | kernel-tools | 0 |
| amazon:2 | perf | 0 |
| amazon:2 | kernel-livepatch-4.14.309-231.529 | 0 |
| Linux | Linux | 3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5, 3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5, 0 |
| amazon:2 | python-perf | 0 |
| amazon:2 | kernel | 0 |
| amazon:2 | kernel-tools-devel | 0 |
| linux | linux_kernel | 2.6.33, 2.6.33, 2.6.33 |
Timeline
- May 21, 2024 CVE Published
- May 22, 2024 EPSS Score (30 in total, the first dated here)
- Oct 5, 2024 Coalition ESS Score (10 in total, the first dated here)
- Jan 25, 2026 Security Advisory (304 in total, the first dated here)
- Sep 22, 2026 Distribution Patch (208 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2023-52730
vulnetix vdb fixes CVE-2023-52730
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2023-52730/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart