Local crash via stale MPLS sysctl pointer
Published Feb 25, 2023 · Updated Mar 20, 2025
Double free in Linux kernel before 6.1.13 allows local users to crash the kernel while renaming an MPLS-enabled network device. After sysctl registration fails, mpls_dev_sysctl_register leaves mdev->sysctl pointing to freed memory, which unregister cleanup frees again. The path requires low-privileged local access, an MPLS-enabled device rename, and a sysctl-table allocation failure; the documented impact is service interruption.
Summary
What happened
Double free in Linux kernel before 6.1.13 allows local users to crash the kernel while renaming an MPLS-enabled network device. After sysctl registration fails, mpls_dev_sysctl_register leaves mdev->sysctl pointing to freed memory, which unregister cleanup frees again. The path requires low-privileged local access, an MPLS-enabled device rename, and a sysctl-table allocation failure; the documented impact is service interruption.
The record
- CVE
- CVE-2023-26545
- Published
- Feb 25, 2023
- Updated
- Mar 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 25, 2023CVE publishedPublication date reported by the CVE source.
- Mar 20, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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