{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50767 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50767 is an use after free vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-50767 and fix it if it is affected.\n\nWhat it is: CVE-2022-50767 is an use after free vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-50767 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-50767/ (Markdown: https://insights.sbomify.com/CVE-2022-50767/index.md)","id":"CVE-2022-50767","markdown":"https://insights.sbomify.com/CVE-2022-50767/index.md","name":"CVE-2022-50767","record":{"aliases":["DEBIAN-CVE-2022-50767","GHSA-gvc9-3fj4-7qr5","UBUNTU-CVE-2022-50767"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A use-after-free vulnerability in the Linux kernel smscufx driver allows local attackers to execute arbitrary code or escalate privileges by physically removing a USB device.","user_interaction":"required","vuln_class":"use_after_free"},"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\nfbdev: smscufx: Fix several use-after-free bugs\n\nSeveral types of UAFs can occur when physically removing a USB device.\n\nAdds ufx_ops_destroy() function to .fb_destroy of fb_ops, and\nin this function, there is kref_put() that finally calls ufx_free().\n\nThis fix prevents multiple UAFs.","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":"fbdev: smscufx: Fix several use-after-free bugs","id":"CVE-2022-50767","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2022"},"n_packages":0,"n_references":8,"next":{"headline":"scsi: smartpqi: Correct device removal for multi-actuator devices","id":"CVE-2022-50768"},"packages":[],"prev":{"headline":"btrfs: set generation before calling btrfs_clean_tree_block in btrfs_init_new_buffer","id":"CVE-2022-50766"},"products":["Linux"],"published":"2025-12-24","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":"A use-after-free vulnerability in the Linux kernel smscufx driver allows local attackers to execute arbitrary code or escalate privileges by physically removing a USB device.","url":"https://insights.sbomify.com/CVE-2022-50767/"}