Local service interruption via leaked device-tree reference
Published Jun 18, 2025 · Updated May 11, 2026
A reference-count leak in the Linux kernel UCC UART driver allows local users to interrupt service by retaining device-tree resources. During SoC identification, soc_info() retains the reference returned by of_find_node_by_type() because it fails to call of_node_put() after reading the node name. Exploitation requires local low-privileged access and a system using the affected Freescale QUICC Engine UCC UART driver; the consequence is limited to service interruption.
Summary
What happened
A reference-count leak in the Linux kernel UCC UART driver allows local users to interrupt service by retaining device-tree resources. During SoC identification, soc_info() retains the reference returned by of_find_node_by_type() because it fails to call of_node_put() after reading the node name. Exploitation requires local low-privileged access and a system using the affected Freescale QUICC Engine UCC UART driver; the consequence is limited to service interruption.
The record
- CVE
- CVE-2022-50019
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=2.6.25
- Affected versionversion=d7584ed2b994a572326650b0c4d2c25961e6f49d <17c32546166d8a7d2579c4b57c8b16241f94a66b
- Affected versionversion=d7584ed2b994a572326650b0c4d2c25961e6f49d <59bc4c19d53bdac61ec952c01c6e864f5f0f8367
- Affected versionversion=d7584ed2b994a572326650b0c4d2c25961e6f49d <81939c4fbc2d5c754d0f1c1f05149d4b70d751ed
- Affected versionversion=d7584ed2b994a572326650b0c4d2c25961e6f49d <8245e7d1d7f75a9255ad1e8146752e5051d528b8
- Affected versionversion=d7584ed2b994a572326650b0c4d2c25961e6f49d <ca3fc1c38e4253bc019881301a28ea60b8b0bca3
- Affected versionversion=d7584ed2b994a572326650b0c4d2c25961e6f49d <d24d7bb2cd947676f9b71fb944d045e09b8b282f
- Affected versionversion=d7584ed2b994a572326650b0c4d2c25961e6f49d <ec56f886f3bf0f15f7a3844d4c025e165b8e8de7
- Affected versionversion=d7584ed2b994a572326650b0c4d2c25961e6f49d <f6ed634eedb1a8a6a8cb110a7695c7abb70ffcbf
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