Invalid kernel memory access via premature rbd ownership
Published Sep 16, 2025 · Updated May 11, 2026
Use-after-free in the Linux kernel rbd driver allows local users to access freed memory when rbd device creation fails. The do_rbd_add() path retains rbd_client, spec, and opts after rbd_dev_create() prematurely takes ownership and frees them on ID-allocation or work-queue setup failure. Reachability requires local privileges to request an rbd device and the exceptional creation failure; the published record demonstrates no bounded effect beyond invalid kernel memory access.
Summary
What happened
Use-after-free in the Linux kernel rbd driver allows local users to access freed memory when rbd device creation fails. The do_rbd_add() path retains rbd_client, spec, and opts after rbd_dev_create() prematurely takes ownership and frees them on ID-allocation or work-queue setup failure. Reachability requires local privileges to request an rbd device and the exceptional creation failure; the published record demonstrates no bounded effect beyond invalid kernel memory access.
The record
- CVE
- CVE-2023-53307
- Published
- Sep 16, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1643dfa4c2c827d6e2aa419df8c17b0f24090278 <71da2a151ed1adb0aea4252b16d81b53012e7afd
- Affected versionversion=1643dfa4c2c827d6e2aa419df8c17b0f24090278 <9787b328c42c13c4f31e7d5042c4e877e9344068
- Affected versionversion=1643dfa4c2c827d6e2aa419df8c17b0f24090278 <a73783e4e0c4d1507794da211eeca75498544dff
- Affected versionversion=1643dfa4c2c827d6e2aa419df8c17b0f24090278 <ae16346078b1189aee934afd872d9f3d0a682c33
- Affected versionversion=1643dfa4c2c827d6e2aa419df8c17b0f24090278 <cc8c0dd2984503ed09efa37bcafcef3d3da104e8
- Affected versionversion=1643dfa4c2c827d6e2aa419df8c17b0f24090278 <e3cbb4d60764295992c95344f2d779439e8b34ce
- Affected versionversion=1643dfa4c2c827d6e2aa419df8c17b0f24090278 <f7c4d9b133c7a04ca619355574e96b6abf209fba
- Affected versionversion=1643dfa4c2c827d6e2aa419df8c17b0f24090278 <faa7b683e436664fff5648426950718277831348
- Affected versionversion=4.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo