Service interruption via unreleased platform devices
Published Sep 15, 2025 · Updated Sep 15, 2025
Resource leak in the MIPS SGI-IP27 bridge code in Linux allows local users to interrupt service through repeated device-registration failures. On bridge setup error paths, bridge_platform_create() returns after a platform-device operation fails without releasing the device; a later xtalk-bridge failure also leaves sgi_w1 resources registered. Reachability requires an SGI-IP27 system and local low-privileged access capable of repeatedly reaching those failure paths; the documented consequence is availability loss without confidentiality or integrity impact.
Summary
What happened
Resource leak in the MIPS SGI-IP27 bridge code in Linux allows local users to interrupt service through repeated device-registration failures. On bridge setup error paths, bridge_platform_create() returns after a platform-device operation fails without releasing the device; a later xtalk-bridge failure also leaves sgi_w1 resources registered. Reachability requires an SGI-IP27 system and local low-privileged access capable of repeatedly reaching those failure paths; the documented consequence is availability loss without confidentiality or integrity impact.
The record
- CVE
- CVE-2022-50281
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 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=5.5
- Affected versionversion=5dc76a96e95ae041c1d8e52714bd77576b35919b <11bec9cba4de06b3c0e9e4041453c2caaa1cbec1
- Affected versionversion=5dc76a96e95ae041c1d8e52714bd77576b35919b <48025893b3e31b917ad654d28d23fff66681cac4
- Affected versionversion=5dc76a96e95ae041c1d8e52714bd77576b35919b <93296e7ab774230b7c36541dead10b6da39b650f
- Affected versionversion=5dc76a96e95ae041c1d8e52714bd77576b35919b <d7ac29e60d0ff71e9e414af595b8c92800f7fa90
- Affected versionversion=5dc76a96e95ae041c1d8e52714bd77576b35919b <da2aecef866b476438d02c662507a0e4e818da9d
What conditions does exploitation require?
What is affected?
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