{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50847 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50847 is a vulnerability in Linux, published on 30 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-50847 and fix it if it is affected.\n\nWhat it is: CVE-2022-50847 is a vulnerability in Linux, published on 30 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-50847 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-50847/ (Markdown: https://insights.sbomify.com/CVE-2022-50847/index.md)","id":"CVE-2022-50847","markdown":"https://insights.sbomify.com/CVE-2022-50847/index.md","name":"CVE-2022-50847","record":{"aliases":["DEBIAN-CVE-2022-50847","GHSA-78f2-hq34-889m","UBUNTU-CVE-2022-50847"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A local attacker can trigger a kernel crash via a NULL pointer dereference in the it6505 DRM bridge driver during boot.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\ndrm/bridge: it6505: Initialize AUX channel in it6505_i2c_probe\n\nDuring device boot, the HPD interrupt could be triggered before the DRM\nsubsystem registers it6505 as a DRM bridge. In such cases, the driver\ntries to access AUX channel and causes NULL pointer dereference.\nInitializing the AUX channel earlier to prevent such error.","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":"drm/bridge: it6505: Initialize AUX channel in it6505_i2c_probe","id":"CVE-2022-50847","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"drivers: dio: fix possible memory leak in dio_init()","id":"CVE-2022-50848"},"packages":[],"prev":{"headline":"mmc: via-sdmmc: fix return value check of mmc_add_host()","id":"CVE-2022-50846"},"products":["Linux"],"published":"2025-12-30","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 local attacker can trigger a kernel crash via a NULL pointer dereference in the it6505 DRM bridge driver during boot.","url":"https://insights.sbomify.com/CVE-2022-50847/"}