Logical-partition registration failure via duplicate device names
Published Sep 15, 2025 · Updated Sep 15, 2025
Improper device naming in Linux kernel ARM FF-A support allows local users to block logical-partition service registration. ffa_device_register() builds each device name from the physical partition's VM ID alone, so a second UUID-backed service collides in sysfs and device_register() returns EEXIST. The condition requires an ARM FF-A partition exposing multiple services under one VM ID; the public record does not establish how local users control that partition data, and the bounded result is failure to register additional services.
Summary
What happened
Improper device naming in Linux kernel ARM FF-A support allows local users to block logical-partition service registration. ffa_device_register() builds each device name from the physical partition's VM ID alone, so a second UUID-backed service collides in sysfs and device_register() returns EEXIST. The condition requires an ARM FF-A partition exposing multiple services under one VM ID; the public record does not establish how local users control that partition data, and the bounded result is failure to register additional services.
The record
- CVE
- CVE-2023-53256
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 2025Record 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=5.14
- Affected versionversion=e781858488b918e30a6ff28e9eab6058b787e3b3 <19b8766459c41c6f318f8a548cc1c66dffd18363
- Affected versionversion=e781858488b918e30a6ff28e9eab6058b787e3b3 <93d0cbe88118fcef234d3ebcbdadcb9ebe9d34f1
- Affected versionversion=e781858488b918e30a6ff28e9eab6058b787e3b3 <c2f65991097a62efbdb2bed3c06fc86b08c9593b
- Affected versionversion=e781858488b918e30a6ff28e9eab6058b787e3b3 <dfc5aaa57f52a5800c339369d235fa30fb734feb
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
No sourced classifications are available.
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