Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-safety flaw in the RBD driver error path. A local, low-privileged user could potentially trigger a use-after-free when RBD device creation fails, with possible full confidentiality, integrity, and availability impact according to CVSS.
Executive priority
Treat as high priority for shared Linux infrastructure or systems exposing local shell access. It is not remotely reachable from the supplied evidence, but kernel memory corruption with high impact warrants timely patch validation.
Technical view
CVE-2023-53307 is CWE-416 in Linux kernel rbd do_rbd_add(). If rbd_dev_create() fails while getting an ID or setting up a work queue, ownership is transferred too early and freed structures may be reused by the caller.
Likely exposure
Exposure is most relevant to Linux systems with affected kernel builds where the rbd driver code is present and local users have a path to exercise RBD device creation. Distribution backports may change exposure, so package-level advisory checks are necessary.
Exploitation context
The CVSS vector is local, low complexity, low privilege, and no user interaction. The bundle says KEV is false and provides no public exploitation evidence, so active exploitation is not established from these sources.
Researcher notes
The root cause is premature ownership transfer of rbd_client, spec, and opts before rbd_dev_create() can fail and free rbd_dev. The source bundle credits Linux Verification Center using SVACE and references multiple stable commits.
Mitigation direction
- Apply kernel updates or vendor packages containing the referenced Linux stable fixes.
- Check distribution advisories for backported fixes matching CVE-2023-53307.
- Restrict local access to systems where untrusted users can reach RBD workflows.
- Prioritize affected hosts using Ceph RBD or loading the rbd kernel module.
Validation and detection
- Inventory Linux kernel versions and package release notes across managed hosts.
- Check whether the rbd module is present, loaded, or operationally required.
- Compare kernel source or changelog against the referenced stable commit IDs.
- Confirm vulnerability scanner findings with vendor advisory status, not version strings alone.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-53307 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/71da2a151ed1adb0aea4252b16d81b53012e7afdCVE reference, Linux
- https://git.kernel.org/stable/c/e3cbb4d60764295992c95344f2d779439e8b34ceCVE reference, Linux
- https://git.kernel.org/stable/c/9787b328c42c13c4f31e7d5042c4e877e9344068CVE reference, Linux
- https://git.kernel.org/stable/c/ae16346078b1189aee934afd872d9f3d0a682c33CVE reference, Linux
- https://git.kernel.org/stable/c/a73783e4e0c4d1507794da211eeca75498544dffCVE reference, Linux
- https://git.kernel.org/stable/c/faa7b683e436664fff5648426950718277831348CVE reference, Linux
- https://git.kernel.org/stable/c/cc8c0dd2984503ed09efa37bcafcef3d3da104e8CVE reference, Linux
- https://git.kernel.org/stable/c/f7c4d9b133c7a04ca619355574e96b6abf209fbaCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.