Skip to main content
VulnerabilityPublished Updated

CVE-2026-53025: Linux kernel · greybus: raw: fix use-after-free on cdev close

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High · fixed in ef2d97c15b19b3489de01695bce478601e236c3e : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in ef2d97c15b19b3489de01695bce478601e236c3e, e72ffe59e48a74a8d9220f5ca1d03f2194d882f0, e4d07fd4e30024a4a15094ef2c404197667c857e +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e806c7fb8e9bae87fc23958c3789f2c2f96f54a4, < ef2d97c15b19b3489de01695bce478601e236c3e
Fixed in
  • ef2d97c15b19b3489de01695bce478601e236c3e
LinuxLinuxAffected
  • ≥ e806c7fb8e9bae87fc23958c3789f2c2f96f54a4, < e72ffe59e48a74a8d9220f5ca1d03f2194d882f0
Fixed in
  • e72ffe59e48a74a8d9220f5ca1d03f2194d882f0
LinuxLinuxAffected
  • ≥ e806c7fb8e9bae87fc23958c3789f2c2f96f54a4, < e4d07fd4e30024a4a15094ef2c404197667c857e
Fixed in
  • e4d07fd4e30024a4a15094ef2c404197667c857e
LinuxLinuxAffected
  • ≥ e806c7fb8e9bae87fc23958c3789f2c2f96f54a4, < 983cc2c7efbce04ecbf6328448d895044dd6ab31
Fixed in
  • 983cc2c7efbce04ecbf6328448d895044dd6ab31
LinuxLinuxAffected
  • ≥ e806c7fb8e9bae87fc23958c3789f2c2f96f54a4, < 3abf97a03f4abce1dc3639eea2fcd4bd747b3308
Fixed in
  • 3abf97a03f4abce1dc3639eea2fcd4bd747b3308
LinuxLinuxAffected
  • =4.9
Fixed in–

Description

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.

References

Community reviews

Loading reviews…