CVE-2026-53024

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> greybus: raw: fix use-after-free if write is called after disconnect<br /> <br /> If a user writes to the chardev after disconnect has been called, the<br /> kernel panics with the following trace (with<br /> CONFIG_INIT_ON_FREE_DEFAULT_ON=y):<br /> <br /> BUG: kernel NULL pointer dereference, address: 0000000000000218<br /> ...<br /> Call Trace:<br /> <br /> gb_operation_create_common+0x61/0x180<br /> gb_operation_create_flags+0x28/0xa0<br /> gb_operation_sync_timeout+0x6f/0x100<br /> raw_write+0x7b/0xc7 [gb_raw]<br /> vfs_write+0xcf/0x420<br /> ? task_mm_cid_work+0x136/0x220<br /> ksys_write+0x63/0xe0<br /> do_syscall_64+0xa4/0x290<br /> entry_SYSCALL_64_after_hwframe+0x77/0x7f<br /> <br /> Disconnect calls gb_connection_destroy, which ends up freeing the<br /> connection object. When gb_operation_sync is called in the write file<br /> operations, its gets a freed connection as parameter and the kernel<br /> panics.<br /> <br /> The gb_connection_destroy cannot be moved out of the disconnect<br /> function, as the Greybus subsystem expect all connections belonging to a<br /> bundle to be destroyed when disconnect returns.<br /> <br /> To prevent this bug, use a rw lock to synchronize access between write<br /> and disconnect. This guarantees that the write function doesn&amp;#39;t try<br /> to use a disconnected connection.