CVE-2024-56534

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> isofs: avoid memory leak in iocharset<br /> <br /> A memleak was found as below:<br /> <br /> unreferenced object 0xffff0000d10164d8 (size 8):<br /> comm "pool-udisksd", pid 108217, jiffies 4295408555<br /> hex dump (first 8 bytes):<br /> 75 74 66 38 00 cc cc cc utf8....<br /> backtrace (crc de430d31):<br /> [] kmemleak_alloc+0xb8/0xc8<br /> [] __kmalloc_node_track_caller_noprof+0x380/0x474<br /> [] kstrdup+0x70/0xfc<br /> [] isofs_parse_param+0x228/0x2c0 [isofs]<br /> [] vfs_parse_fs_param+0xf4/0x164<br /> [] vfs_parse_fs_string+0x8c/0xd4<br /> [] vfs_parse_monolithic_sep+0xb0/0xfc<br /> [] generic_parse_monolithic+0x30/0x3c<br /> [] parse_monolithic_mount_data+0x40/0x4c<br /> [] path_mount+0x6c4/0x9ec<br /> [] do_mount+0xac/0xc4<br /> [] __arm64_sys_mount+0x16c/0x2b0<br /> [] invoke_syscall+0x7c/0x104<br /> [] el0_svc_common.constprop.1+0xe0/0x104<br /> [] do_el0_svc+0x2c/0x38<br /> [] el0_svc+0x3c/0x1b8<br /> <br /> The opt-&gt;iocharset is freed inside the isofs_fill_super function,<br /> But there may be situations where it&amp;#39;s not possible to<br /> enter this function.<br /> <br /> For example, in the get_tree_bdev_flags function,when<br /> encountering the situation where "Can&amp;#39;t mount, would change RO state,"<br /> In such a case, isofs_fill_super will not have the opportunity<br /> to be called,which means that opt-&gt;iocharset will not have the chance<br /> to be freed,ultimately leading to a memory leak.<br /> <br /> Let&amp;#39;s move the memory freeing of opt-&gt;iocharset into<br /> isofs_free_fc function.