CVE-2026-53024greybus: raw: fix use-after-free if write is called after disconnect
- 7.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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: <TASK> 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.
Timeline
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 4 months later
· 4 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (19 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 – < 5a6ce05ccd9eca653b09d67eb59026821ffaf61b
- affected e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 – < 966b941ca469fb794637a0803670454f68515e40
- affected e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 – < 2b46f07913a80521ecfe60b229c84bdd7dfb15ab
- affected e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 – < 48d6c32bc049abd114e8f0836c0e7d7cbfba7827
- affected e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 – < 84265cbd96b97058ef67e3f8be3933667a000835
- affected 4.9
- unaffected < 4.9
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 7.0.10 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References5
- https://git.kernel.org/stable/c/5a6ce05ccd9eca653b09d67eb59026821ffaf61b (opens in a new tab)
- https://git.kernel.org/stable/c/966b941ca469fb794637a0803670454f68515e40 (opens in a new tab)
- https://git.kernel.org/stable/c/2b46f07913a80521ecfe60b229c84bdd7dfb15ab (opens in a new tab)
- https://git.kernel.org/stable/c/48d6c32bc049abd114e8f0836c0e7d7cbfba7827 (opens in a new tab)
- https://git.kernel.org/stable/c/84265cbd96b97058ef67e3f8be3933667a000835 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-38892 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-53024)Record last updated .