greybus: raw: fix use-after-free on cdev close
CVE-2026-53025 · published 24 Jun 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-53025?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 to < e4d07fd4e30024a4a15094ef2c404197667c857e, e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 to < 3abf97a03f4abce1dc3639eea2fcd4bd747b3308, e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 to < e72ffe59e48a74a8d9220f5ca1d03f2194d882f0, e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 to < ef2d97c15b19b3489de01695bce478601e236c3e
- Linux Linux: 4.9
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
greybus: raw: fix use-after-free on cdev close
This addresses a use-after-free bug when a raw bundle is disconnected
but its chardev is still opened by an application. When the application
releases the cdev, it causes the following panic when init on free is
enabled (CONFIG_INIT_ON_FREE_DEFAULT_ON=y):
refcount_t: underflow; use-after-free.
WARNING: CPU: 0 PID: 139 at lib/refcount.c:28 refcount_warn_saturate+0xd0/0x130
...
Call Trace:
<TASK>
cdev_put+0x18/0x30
__fput+0x255/0x2a0
__x64_sys_close+0x3d/0x80
do_syscall_64+0xa4/0x290
entry_SYSCALL_64_after_hwframe+0x77/0x7f
The cdev is contained in the "gb_raw" structure, which is freed in the
disconnect operation. When the cdev is released at a later time,
cdev_put gets an address that points to freed memory.
To fix this use-after-free, convert the struct device from a pointer to
being embedded, that makes the lifetime of the cdev and of this device
the same. Then, use cdev_device_add, which guarantees that the device
won't be released until all references to the cdev have been released.
Finally, delegate the freeing of the structure to the device release
function, instead of freeing immediately in the disconnect callback.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/e4d07fd4e30024a4a15094ef2c404197667c857e
- git.kernel.org/stable/c/3abf97a03f4abce1dc3639eea2fcd4bd747b3308
- git.kernel.org/stable/c/e72ffe59e48a74a8d9220f5ca1d03f2194d882f0
- git.kernel.org/stable/c/ef2d97c15b19b3489de01695bce478601e236c3e
- git.kernel.org/stable/c/983cc2c7efbce04ecbf6328448d895044dd6ab31
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON