Not yet scoredPublished Dec 8, 2025

CVE-2022-50636PCI: Fix pci_device_is_present() for VFs by checking PF

Updated under an hour ago (Oct 28, 2026, 4:10 AM ET)

Does this affect you?

It affects Linux. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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]

CVSS: Not yet scored
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Deferred
Record last updated: May 11, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from 8496e85c20e7836b3dec97780e40f420a3ae2801 before f4b44c7766dae2b8681f621941cabe9f14066d59; 8496e85c20e7836b3dec97780e40f420a3ae2801 builds before 643d77fda08d06f863af35e80a7e517ea61d9629; 8496e85c20e7836b3dec97780e40f420a3ae2801 builds before 65bd0962992abd42e77a05e68c7b40e7c73726d1; 8496e85c20e7836b3dec97780e40f420a3ae2801 builds before 99ef6cc791584495987dd11b14769b450dfa5820; 8496e85c20e7836b3dec97780e40f420a3ae2801 builds before 67fd41bbb0f51aa648a47f728b99e6f1fa2ccc34; from 8496e85c20e7836b3dec97780e40f420a3ae2801 before 81565e51ccaf6fff8910e997ee22e16b5e1dabc3; from 8496e85c20e7836b3dec97780e40f420a3ae2801 before 518573988a2f14f517403db2ece5ddaefba21e94; 8496e85c20e7836b3dec97780e40f420a3ae2801 builds before 98b04dd0b4577894520493d96bc4623387767445	CNA record

References

References

https://git.kernel.org/stable/c/f4b44c7766dae2b8681f621941cabe9f14066d59
https://git.kernel.org/stable/c/643d77fda08d06f863af35e80a7e517ea61d9629
https://git.kernel.org/stable/c/65bd0962992abd42e77a05e68c7b40e7c73726d1
https://git.kernel.org/stable/c/99ef6cc791584495987dd11b14769b450dfa5820
https://git.kernel.org/stable/c/67fd41bbb0f51aa648a47f728b99e6f1fa2ccc34
https://git.kernel.org/stable/c/81565e51ccaf6fff8910e997ee22e16b5e1dabc3
https://git.kernel.org/stable/c/518573988a2f14f517403db2ece5ddaefba21e94
https://git.kernel.org/stable/c/98b04dd0b4577894520493d96bc4623387767445

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.