5G registration denial via stale AMF contexts
Published Aug 30, 2026 · Updated Aug 30, 2026
Improper resource release in Linux Foundation Magma 1.9.0 allows remote authenticated users to block 5G device registrations. The AMF termination path fails to remove gNB and UE contexts, leaving a reused RAN_UE_NGAP_ID permanently marked as occupied. The flaw requires a gNB association and reused identifier; affected devices remain unable to register until the AMF context is reset.
Summary
What happened
Improper resource release in Linux Foundation Magma 1.9.0 allows remote authenticated users to block 5G device registrations. The AMF termination path fails to remove gNB and UE contexts, leaving a reused RAN_UE_NGAP_ID permanently marked as occupied. The flaw requires a gNB association and reused identifier; affected devices remain unable to register until the AMF context is reset.
The record
- CVE
- CVE-2026-82552
- Published
- Aug 30, 2026
- Updated
- Aug 30, 2026
- Vendor
- Linux Foundation
- Product
- Magma
- Classifications
- CWE-404, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 30, 2026CVE publishedPublication date reported by the CVE source.
- Aug 30, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.9.0
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
- gNB restart and identifier-reuse reproductionproof of concept · demonstrated
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