Root escalation via configuration-file ownership race
Published Sep 13, 2026 · Updated Sep 13, 2026
Privilege escalation in FRRouting FRR before 8.4 allows local users with the FRR service account to gain root access via a file race. The startup scripts create missing configuration files with touch and then change ownership separately, allowing replacement by a symlink in the gap. Access as the FRR service user and write access to /etc/frr are required; a winning race changes ownership of an attacker-chosen file.
Summary
What happened
Privilege escalation in FRRouting FRR before 8.4 allows local users with the FRR service account to gain root access via a file race. The startup scripts create missing configuration files with touch and then change ownership separately, allowing replacement by a symlink in the gap. Access as the FRR service user and write access to /etc/frr are required; a winning race changes ownership of an attacker-chosen file.
The record
- CVE
- CVE-2022-42917
- Published
- Sep 13, 2026
- Updated
- Sep 13, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 13, 2026CVE publishedPublication date reported by the CVE source.
- Sep 13, 2026Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
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