{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50636 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50636 is a denial of service vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-50636 and fix it if it is affected.\n\nWhat it is: CVE-2022-50636 is a denial of service vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-50636 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-50636/ (Markdown: https://insights.sbomify.com/CVE-2022-50636/index.md)","id":"CVE-2022-50636","markdown":"https://insights.sbomify.com/CVE-2022-50636/index.md","name":"CVE-2022-50636","record":{"aliases":["DEBIAN-CVE-2022-50636","GHSA-m8h5-vf45-h85r","UBUNTU-CVE-2022-50636"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"Local attackers with high privileges can cause a denial of service by triggering a hang in virtio I/O operations during driver unbinding or VF removal.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nPCI: Fix pci_device_is_present() for VFs by checking PF\n\npci_device_is_present() previously didn't work for VFs because it reads the\nVendor and Device ID, which are 0xffff for VFs, which looks like they\naren't present.  Check the PF instead.\n\nWei Gong reported that if virtio I/O is in progress when the driver is\nunbound or \"0\" is written to /sys/.../sriov_numvfs, the virtio I/O\noperation hangs, which may result in output like this:\n\n  task:bash state:D stack:    0 pid: 1773 ppid:  1241 flags:0x00004002\n  Call Trace:\n   schedule+0x4f/0xc0\n   blk_mq_freeze_queue_wait+0x69/0xa0\n   blk_mq_freeze_queue+0x1b/0x20\n   blk_cleanup_queue+0x3d/0xd0\n   virtblk_remove+0x3c/0xb0 [virtio_blk]\n   virtio_dev_remove+0x4b/0x80\n   ...\n   device_unregister+0x1b/0x60\n   unregister_virtio_device+0x18/0x30\n   virtio_pci_remove+0x41/0x80\n   pci_device_remove+0x3e/0xb0\n\nThis happened because pci_device_is_present(VF) returned \"false\" in\nvirtio_pci_remove(), so it called virtio_break_device().  The broken vq\nmeant that vring_interrupt() skipped the vq.callback() that would have\ncompleted the virtio I/O operation via virtblk_done().\n\n[bhelgaas: commit log, simplify to always use pci_physfn(), add stable tag]","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"PCI: Fix pci_device_is_present() for VFs by checking PF","id":"CVE-2022-50636","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":8,"next":{"headline":"cpufreq: qcom-hw: Fix memory leak in qcom_cpufreq_hw_read_lut()","id":"CVE-2022-50637"},"packages":[],"prev":{"headline":"powerpc/kprobes: Fix null pointer reference in arch_prepare_kprobe()","id":"CVE-2022-50635"},"products":["Linux"],"published":"2025-12-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"Local attackers with high privileges can cause a denial of service by triggering a hang in virtio I/O operations during driver unbinding or VF removal.","url":"https://insights.sbomify.com/CVE-2022-50636/"}