CVE-2012-4516: librdmacm 1.0.16, when ibacm.port is not specified, connects to port 6125, which allows remote attackers to sp
CVE-2012-4516 is a medium-severity flaw (CVSS 5.8) affecting librdmacm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
librdmacm 1.0.16, when ibacm.port is not specified, connects to port 6125, which allows remote attackers to specify the address resolution information for the application via a malicious ib_acm service.
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 5.8 (Medium) |
| EPSS exploit chance | 2.1% (top 18%) |
| CISA exploited list | No |
| Published | 2012-10-22 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2012-4516?
librdmacm: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2012-4516 being exploited?
CVE-2012-4516 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2012-4516 affect?
CVE-2012-4516 affects librdmacm. Severity is medium (CVSS 5.8). librdmacm 1.0.16, when ibacm.port is not specified, connects to port 6125, which allows remote attackers to specify the address resolution information for the application via a malicious ib_acm service.
How urgent is CVE-2012-4516?
Priority 41/100. No elevated risk signals yet.