Kernel resource exhaustion via leaked GID references
Published Dec 24, 2025 · Updated Dec 24, 2025
A reference leak in Linux RDMA/core allows local users to exhaust kernel resources by repeatedly triggering failed address-handle creation. In drivers/infiniband/core/verbs.c, the address-handle creation error path returns without releasing sgid_attr, leaving a GID-table reference held. A local low-privileged user must be able to submit RDMA address-handle creation requests and force them to fail; repeated failures consume kernel resources and can interrupt service.
Summary
What happened
A reference leak in Linux RDMA/core allows local users to exhaust kernel resources by repeatedly triggering failed address-handle creation. In drivers/infiniband/core/verbs.c, the address-handle creation error path returns without releasing sgid_attr, leaving a GID-table reference held. A local low-privileged user must be able to submit RDMA address-handle creation requests and force them to fail; repeated failures consume kernel resources and can interrupt service.
The record
- CVE
- CVE-2023-54003
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 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=1a1f460ff151710289c2f8d4badd8b603b87d610 <370280c65c28a515b841c9f2c08524f06182510c
- Affected versionversion=1a1f460ff151710289c2f8d4badd8b603b87d610 <632d6baf8884d803e598bf5164008d23fd9b736c
- Affected versionversion=1a1f460ff151710289c2f8d4badd8b603b87d610 <9c46c49ad3ffe84121715d392b5a0a94f9f10669
- Affected versionversion=1a1f460ff151710289c2f8d4badd8b603b87d610 <aca3b0fa3d04b40c96934d86cc224cccfa7ea8e0
- Affected versionversion=1a1f460ff151710289c2f8d4badd8b603b87d610 <d1b9b3191697a80aca8e247320eba46f24d41d18
- Affected versionversion=1a1f460ff151710289c2f8d4badd8b603b87d610 <e97ff11b396c320d2cc025b09741ba432fcb20a2
- Affected versionversion=4.19
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.
Weakness, pattern, technique
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