Service interruption via leaked PCI device references
Published Oct 22, 2025 · Updated Oct 22, 2025
Resource leakage in the PCH UART driver in Linux allows local users to interrupt service by exhausting kernel PCI-device references. pch_request_dma() calls pci_get_slot(), which increments dma_dev's reference count, but omits pci_dev_put() on normal and error exits. The path requires local low-privileged access and a system using the PCH UART driver; repeated triggering depletes kernel resources, with no network or confidentiality impact reported.
Summary
What happened
Resource leakage in the PCH UART driver in Linux allows local users to interrupt service by exhausting kernel PCI-device references. pch_request_dma() calls pci_get_slot(), which increments dma_dev's reference count, but omits pci_dev_put() on normal and error exits. The path requires local low-privileged access and a system using the PCH UART driver; repeated triggering depletes kernel resources, with no network or confidentiality impact reported.
The record
- CVE
- CVE-2022-50576
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 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=2.6.38
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <07f4ca68b0f6bf84b6b391c14b59fd179fcde9c5
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <4f5d28865c665c9064de631a518f9bc8099d9ce4
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <516614a371c26e3334625b4bca19a5362bf658d6
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <56e5a7c5ee3f0dc8978b5df2b1a98a1b060c5e2a
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <6f7d82380fbeaed3a940efc33c23f0c4bbd0fc02
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <8be3a7bf773700534a6e8f87f6ed2ed111254be5
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <90ff030ca10b69feeebda1427550ebf9ed2ad868
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <d165388227aa7e46a9751b90bae6337b5335cdbb
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <dfd15c5550b9190d5b0f9bcacb3e6436322f3854
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
No sourced classifications are available.
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