| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-56534: isofs: avoid memory leak in iocharset |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| isofs: avoid memory leak in iocharset |
| |
| A memleak was found as below: |
| |
| unreferenced object 0xffff0000d10164d8 (size 8): |
| comm "pool-udisksd", pid 108217, jiffies 4295408555 |
| hex dump (first 8 bytes): |
| 75 74 66 38 00 cc cc cc utf8.... |
| backtrace (crc de430d31): |
| [<ffff800081046e6c>] kmemleak_alloc+0xb8/0xc8 |
| [<ffff8000803e6c3c>] __kmalloc_node_track_caller_noprof+0x380/0x474 |
| [<ffff800080363b74>] kstrdup+0x70/0xfc |
| [<ffff80007bb3c6a4>] isofs_parse_param+0x228/0x2c0 [isofs] |
| [<ffff8000804d7f68>] vfs_parse_fs_param+0xf4/0x164 |
| [<ffff8000804d8064>] vfs_parse_fs_string+0x8c/0xd4 |
| [<ffff8000804d815c>] vfs_parse_monolithic_sep+0xb0/0xfc |
| [<ffff8000804d81d8>] generic_parse_monolithic+0x30/0x3c |
| [<ffff8000804d8bfc>] parse_monolithic_mount_data+0x40/0x4c |
| [<ffff8000804b6a64>] path_mount+0x6c4/0x9ec |
| [<ffff8000804b6e38>] do_mount+0xac/0xc4 |
| [<ffff8000804b7494>] __arm64_sys_mount+0x16c/0x2b0 |
| [<ffff80008002b8dc>] invoke_syscall+0x7c/0x104 |
| [<ffff80008002ba44>] el0_svc_common.constprop.1+0xe0/0x104 |
| [<ffff80008002ba94>] do_el0_svc+0x2c/0x38 |
| [<ffff800081041108>] el0_svc+0x3c/0x1b8 |
| |
| The opt->iocharset is freed inside the isofs_fill_super function, |
| But there may be situations where it's not possible to |
| enter this function. |
| |
| For example, in the get_tree_bdev_flags function,when |
| encountering the situation where "Can't mount, would change RO state," |
| In such a case, isofs_fill_super will not have the opportunity |
| to be called,which means that opt->iocharset will not have the chance |
| to be freed,ultimately leading to a memory leak. |
| |
| Let's move the memory freeing of opt->iocharset into |
| isofs_free_fc function. |
| |
| The Linux kernel CVE team has assigned CVE-2024-56534 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.10 with commit 1b17a46c9243e9421ee1ac6d628604bbc4ae2201 and fixed in 6.11.11 with commit 34f090ddb3630a26e5a6b220bf3bfaf5c7b70393 |
| Issue introduced in 6.10 with commit 1b17a46c9243e9421ee1ac6d628604bbc4ae2201 and fixed in 6.12.2 with commit 0fbab266ca8000333c966f5b58cb9b9cac658573 |
| Issue introduced in 6.10 with commit 1b17a46c9243e9421ee1ac6d628604bbc4ae2201 and fixed in 6.13 with commit 0b5bbeee4de616a268db77e2f40f19ab010a367b |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2024-56534 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| fs/isofs/inode.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/34f090ddb3630a26e5a6b220bf3bfaf5c7b70393 |
| https://git.kernel.org/stable/c/0fbab266ca8000333c966f5b58cb9b9cac658573 |
| https://git.kernel.org/stable/c/0b5bbeee4de616a268db77e2f40f19ab010a367b |
