{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68755 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68755 is a vulnerability in Linux, published on 5 Jan 2026. 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-2025-68755 and fix it if it is affected.\n\nWhat it is: CVE-2025-68755 is a vulnerability in Linux, published on 5 Jan 2026. 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-2025-68755 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-2025-68755/ (Markdown: https://insights.sbomify.com/CVE-2025-68755/index.md)","id":"CVE-2025-68755","markdown":"https://insights.sbomify.com/CVE-2025-68755/index.md","name":"CVE-2025-68755","record":{"aliases":["BELL-CVE-2025-68755","DEBIAN-CVE-2025-68755","GHSA-7g54-f344-23m9","ROOT-OS-DEBIAN-11-CVE-2025-68755","ROOT-OS-DEBIAN-12-CVE-2025-68755","ROOT-OS-DEBIAN-13-CVE-2025-68755","ROOT-OS-UBUNTU-2204-CVE-2025-68755","ROOT-OS-UBUNTU-2404-CVE-2025-68755","UBUNTU-CVE-2025-68755"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A NULL pointer dereference in the Linux kernel MOST I2C driver causes a system crash if the driver is probed, requiring local access or specific hardware configuration.","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\nstaging: most: remove broken i2c driver\n\nThe MOST I2C driver has been completely broken for five years without\nanyone noticing so remove the driver from staging.\n\nSpecifically, commit 723de0f9171e (\"staging: most: remove device from\ninterface structure\") started requiring drivers to set the interface\ndevice pointer before registration, but the I2C driver was never updated\nwhich results in a NULL pointer dereference if anyone ever tries to\nprobe it.","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":"staging: most: remove broken i2c driver","id":"CVE-2025-68755","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"block: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u003etag_list_lock","id":"CVE-2025-68756"},"packages":[],"prev":{"headline":"rtc: amlogic-a4: fix double free caused by devm","id":"CVE-2025-68754"},"products":["Linux"],"published":"2026-01-05","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-10-21","vendors":["Linux"]},"summary":"A NULL pointer dereference in the Linux kernel MOST I2C driver causes a system crash if the driver is probed, requiring local access or specific hardware configuration.","url":"https://insights.sbomify.com/CVE-2025-68755/"}