Service interruption via probe-path reference leak
Published Dec 24, 2025 · Updated Dec 24, 2025
Resource leak in the Xilinx GMII-to-RGMII PHY driver in affected Linux kernels allows local users to interrupt service through device probing. The xgmiitorgmii_probe function obtains a referenced PHY device with of_phy_find_device but omits put_device after use, retaining each device reference. Triggering the affected probe path requires local low-privileged access and the relevant Xilinx PHY configuration; repeated leaks can exhaust resources and disrupt availability.
Summary
What happened
Resource leak in the Xilinx GMII-to-RGMII PHY driver in affected Linux kernels allows local users to interrupt service through device probing. The xgmiitorgmii_probe function obtains a referenced PHY device with of_phy_find_device but omits put_device after use, retaining each device reference. Triggering the affected probe path requires local low-privileged access and the relevant Xilinx PHY configuration; repeated leaks can exhaust resources and disrupt availability.
The record
- CVE
- CVE-2022-50777
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 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=3f7056e1822d648f8022997497edc6cad2ad1e73 <53526dbc8aa6b95e9fc2ab1e29b1a9145721da24
- Affected versionversion=4.19
- Affected versionversion=900812a0d318954400d20b0190c7d788b4ff2cc2
- Affected versionversion=a5a849c9e8a6c357f84a5e249cb468f20da6d28f
- Affected versionversion=ab4e6ee578e88a659938db8fbf33720bc048d29c <00616bd1913a4f879679e02dc08c2f501ca2bd4c
- Affected versionversion=ab4e6ee578e88a659938db8fbf33720bc048d29c <106d0d33c9d1ec4ddeeffc1fdc717ff09953d4ed
- Affected versionversion=ab4e6ee578e88a659938db8fbf33720bc048d29c <4d112f001612c79927c1ecf29522b34c4fa292e0
- Affected versionversion=ab4e6ee578e88a659938db8fbf33720bc048d29c <52841e71253e6ace72751c72560950474a57d04c
- Affected versionversion=ab4e6ee578e88a659938db8fbf33720bc048d29c <78b0b1ff525d9be4babf5a148a4de0d50042d95d
- Affected versionversion=ab4e6ee578e88a659938db8fbf33720bc048d29c <d039535850ee47079d59527e96be18d8e0daa84b
- Affected versionversion=ab4e6ee578e88a659938db8fbf33720bc048d29c <ee84d37a5f08ed1121cdd16f8f3ed87552087a21
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
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