CVE-2022-50477

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> rtc: class: Fix potential memleak in devm_rtc_allocate_device()<br /> <br /> devm_rtc_allocate_device() will alloc a rtc_device first, and then run<br /> dev_set_name(). If dev_set_name() failed, the rtc_device will memleak.<br /> Move devm_add_action_or_reset() in front of dev_set_name() to prevent<br /> memleak.<br /> <br /> unreferenced object 0xffff888110a53000 (size 2048):<br /> comm "python3", pid 470, jiffies 4296078308 (age 58.882s)<br /> hex dump (first 32 bytes):<br /> 00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff .........0......<br /> 08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00 .0..............<br /> backtrace:<br /> [] kmalloc_trace+0x21/0x110<br /> [] devm_rtc_allocate_device+0xd4/0x400<br /> [] devm_rtc_device_register+0x1a/0x80<br /> [] rx4581_probe+0xdd/0x110 [rtc_rx4581]<br /> [] spi_probe+0xde/0x130<br /> [] really_probe+0x175/0x3f0<br /> [] __driver_probe_device+0xe6/0x170<br /> [] device_driver_attach+0x32/0x80<br /> [] bind_store+0x10b/0x1a0<br /> [] drv_attr_store+0x49/0x70<br /> [] sysfs_kf_write+0x8d/0xb0<br /> [] kernfs_fop_write_iter+0x214/0x2d0<br /> [] vfs_write+0x61a/0x7d0<br /> [] ksys_write+0xc8/0x190<br /> [] do_syscall_64+0x37/0x90<br /> [] entry_SYSCALL_64_after_hwframe+0x63/0xcd