{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68763 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68763 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-68763 and fix it if it is affected.\n\nWhat it is: CVE-2025-68763 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-68763 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-68763/ (Markdown: https://insights.sbomify.com/CVE-2025-68763/index.md)","id":"CVE-2025-68763","markdown":"https://insights.sbomify.com/CVE-2025-68763/index.md","name":"CVE-2025-68763","record":{"aliases":["BELL-CVE-2025-68763","DEBIAN-CVE-2025-68763","GHSA-28vg-cxp3-45wq","ROOT-OS-DEBIAN-13-CVE-2025-68763","ROOT-OS-UBUNTU-2404-CVE-2025-68763","UBUNTU-CVE-2025-68763"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel crypto","requires_auth":"none","summary":"An integer overflow in the StarFive crypto driver mishandles error codes, potentially leading to buffer overflows and system compromise.","user_interaction":"not_required","vuln_class":"integer_overflow"},"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\ncrypto: starfive - Correctly handle return of sg_nents_for_len\n\nThe return value of sg_nents_for_len was assigned to an unsigned long\nin starfive_hash_digest, causing negative error codes to be converted\nto large positive integers.\n\nAdd error checking for sg_nents_for_len and return immediately on\nfailure to prevent potential buffer overflows.","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":"crypto: starfive - Correctly handle return of sg_nents_for_len","id":"CVE-2025-68763","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags","id":"CVE-2025-68764"},"packages":[],"prev":{"headline":"net: netpoll: initialize work queue before error checks","id":"CVE-2025-68762"},"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-05-11","vendors":["Linux"]},"summary":"An integer overflow in the StarFive crypto driver mishandles error codes, potentially leading to buffer overflows and system compromise.","url":"https://insights.sbomify.com/CVE-2025-68763/"}