CVE-2023-53314: fbdev/ep93xx-fb: Do not assign to struct fb_info.dev
In the Linux kernel, the following vulnerability has been resolved:
fbdev/ep93xx-fb: Do not assign to struct fb_info.dev
Do not assing the Linux device to struct fb_info.dev. The call to
register_framebuffer() initializes the field to the fbdev device.
Drivers should not override its value.
Fixes a bug where the driver incorrectly decreases the hardware
device's reference counter and leaks the fbdev device.
v2:
* add Fixes tag (Dan)
Security readout for executives and security teams
Plain-English summary
CVE-2023-53314 is a Linux kernel framebuffer driver bug that can cause availability impact. The issue is local, not network-exposed by itself, and requires low-privileged local access according to the CVSS vector. Business urgency is highest for embedded or specialty Linux systems using the EP93xx framebuffer driver.
Executive priority
Treat as a targeted availability maintenance item, not an emergency internet-wide exposure. Prioritize embedded or operational devices where local denial of service would disrupt service or recovery windows are limited.
Technical view
The ep93xx-fb driver incorrectly assigned the Linux hardware device to struct fb_info.dev. register_framebuffer() should initialize that field to the fbdev device. The bug can incorrectly decrement the hardware device reference counter and leak the fbdev device, producing a local availability risk.
Likely exposure
Exposure is likely limited to Linux systems carrying the affected ep93xx-fb framebuffer driver, especially embedded ARM environments. The source bundle does not identify affected distributions, appliances, or cloud images.
Exploitation context
No active exploitation is supported by the supplied sources, and the CVE is not listed as KEV. The CVSS vector indicates local access, low complexity, low privileges, no user interaction, and high availability impact.
Researcher notes
The available evidence describes a reference-counting/device lifetime bug in fbdev/ep93xx-fb. Sources do not provide exploit details, affected distributions, or standalone mitigations beyond the upstream stable fixes.
Mitigation direction
Apply a vendor kernel update containing the referenced stable fixes.
Check Linux distribution or embedded vendor advisories for backported fixes.
Prioritize systems where ep93xx-fb is present and framebuffer access is enabled.
Plan normal kernel-update reboot and rollback procedures.
Validation and detection
Inventory running kernel versions against the affected version data.
Check whether the ep93xx-fb driver is built, loaded, or required.
Confirm vendor kernel packages include one of the referenced stable fixes.
Run regression testing for display and boot behavior after updating.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cve · low confidence lookup
CVE-2023-53314 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
We 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.