{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50878 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50878 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-50878 and fix it if it is affected.\n\nWhat it is: CVE-2022-50878 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-50878 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-50878/ (Markdown: https://insights.sbomify.com/CVE-2022-50878/index.md)","id":"CVE-2022-50878","markdown":"https://insights.sbomify.com/CVE-2022-50878/index.md","name":"CVE-2022-50878","record":{"aliases":["DEBIAN-CVE-2022-50878","GHSA-hp2j-q336-h2mp","UBUNTU-CVE-2022-50878"],"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 NULL pointer dereference in the Lontium LT9611 GPU driver can cause a system crash, requiring a kernel patch.","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\ngpu: lontium-lt9611: Fix NULL pointer dereference in lt9611_connector_init()\n\nA NULL check for bridge-\u003eencoder shows that it may be NULL, but it\nalready been dereferenced on all paths leading to the check.\n812\tif (!bridge-\u003eencoder) {\n\nDereference the pointer bridge-\u003eencoder.\n810\tdrm_connector_attach_encoder(\u0026lt9611-\u003econnector, bridge-\u003eencoder);","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":"gpu: lontium-lt9611: Fix NULL pointer dereference in lt9611_connector_init()","id":"CVE-2022-50878","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":5,"next":{"headline":"objtool: Fix SEGFAULT","id":"CVE-2022-50879"},"packages":[],"prev":{"headline":"net: broadcom: bcm4908_enet: update TX stats after actual transmission","id":"CVE-2022-50877"},"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 NULL pointer dereference in the Lontium LT9611 GPU driver can cause a system crash, requiring a kernel patch.","url":"https://insights.sbomify.com/CVE-2022-50878/"}