CVE-2022-50636 Details
Description
In the Linux kernel, the following vulnerability has been resolved: PCI: Fix pci_device_is_present() for VFs by checking PF pci_device_is_present() previously didn't work for VFs because it reads the Vendor and Device ID, which are 0xffff for VFs, which looks like they aren't present. Check the PF instead. Wei Gong reported that if virtio I/O is in progress when the driver is unbound or "0" is written to /sys/.../sriov_numvfs, the virtio I/O operation hangs, which may result in output like this: task:bash state:D stack: 0 pid: 1773 ppid: 1241 flags:0x00004002 Call Trace: schedule+0x4f/0xc0 blk_mq_freeze_queue_wait+0x69/0xa0 blk_mq_freeze_queue+0x1b/0x20 blk_cleanup_queue+0x3d/0xd0 virtblk_remove+0x3c/0xb0 [virtio_blk] virtio_dev_remove+0x4b/0x80 ... device_unregister+0x1b/0x60 unregister_virtio_device+0x18/0x30 virtio_pci_remove+0x41/0x80 pci_device_remove+0x3e/0xb0 This happened because pci_device_is_present(VF) returned "false" in virtio_pci_remove(), so it called virtio_break_device(). The broken vq meant that vring_interrupt() skipped the vq.callback() that would have completed the virtio I/O operation via virtblk_done(). [bhelgaas: commit log, simplify to always use pci_physfn(), add stable tag]
A vulnerability in the Linux kernel's PCI subsystem affects the presence check for Virtual Functions (VFs) in the Single Root I/O Virtualization (SR-IOV) framework. The issue arises because the function 'pci_device_is_present()' incorrectly identifies VFs as absent. This misjudgment occurs because the Vendor and Device IDs for VFs are set to '0xffff', which the function interprets as indicating that the devices are not present. The vulnerability can lead to a denial-of-service condition, particularly in scenarios involving virtio I/O operations. When a driver is unbound or when '0' is written to the SR-IOV virtual functions configuration, any ongoing virtio I/O tasks can hang. This situation may disrupt normal operations and cause processes to become unresponsive.
Users can upgrade to the latest stable version of the Linux kernel, where this vulnerability has been addressed. Instructions for downloading the patched kernel can be found on the official Linux kernel website.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 9, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/518573988a2f14f517403db2ece5ddaefba21e94 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/643d77fda08d06f863af35e80a7e517ea61d9629 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/65bd0962992abd42e77a05e68c7b40e7c73726d1 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/67fd41bbb0f51aa648a47f728b99e6f1fa2ccc34 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/81565e51ccaf6fff8910e997ee22e16b5e1dabc3 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/98b04dd0b4577894520493d96bc4623387767445 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/99ef6cc791584495987dd11b14769b450dfa5820 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/f4b44c7766dae2b8681f621941cabe9f14066d59 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 10, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 9, 2025 | New CVE Received | kernel.org |
Volerion