{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68799 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68799 is a high-severity vulnerability in Linux, published on 13 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-68799 and fix it if it is affected.\n\nWhat it is: CVE-2025-68799 is a high-severity vulnerability in Linux, published on 13 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-68799 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-68799/ (Markdown: https://insights.sbomify.com/CVE-2025-68799/index.md)","id":"CVE-2025-68799","markdown":"https://insights.sbomify.com/CVE-2025-68799/index.md","name":"CVE-2025-68799","record":{"aliases":["AZL-74327","BELL-CVE-2025-68799","DEBIAN-CVE-2025-68799","GHSA-pxpq-p89v-xx8g","ROOT-OS-DEBIAN-11-CVE-2025-68799","ROOT-OS-DEBIAN-12-CVE-2025-68799","ROOT-OS-DEBIAN-13-CVE-2025-68799","ROOT-OS-UBUNTU-2204-CVE-2025-68799","ROOT-OS-UBUNTU-2404-CVE-2025-68799","UBUNTU-CVE-2025-68799"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"An attacker can cause kernel instability and potential information disclosure via integer underflow in the CAIF protocol when FCS is disabled.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncaif: fix integer underflow in cffrml_receive()\n\nThe cffrml_receive() function extracts a length field from the packet\nheader and, when FCS is disabled, subtracts 2 from this length without\nvalidating that len \u003e= 2.\n\nIf an attacker sends a malicious packet with a length field of 0 or 1\nto an interface with FCS disabled, the subtraction causes an integer\nunderflow.\n\nThis can lead to memory exhaustion and kernel instability, potential\ninformation disclosure if padding contains uninitialized kernel memory.\n\nFix this by validating that len \u003e= 2 before performing the subtraction.","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":"caif: fix integer underflow in cffrml_receive()","id":"CVE-2025-68799","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats","id":"CVE-2025-68800"},"packages":[],"prev":{"headline":"perf/x86/amd: Check event before enable to avoid GPF","id":"CVE-2025-68798"},"products":["Linux"],"published":"2026-01-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"An attacker can cause kernel instability and potential information disclosure via integer underflow in the CAIF protocol when FCS is disabled.","url":"https://insights.sbomify.com/CVE-2025-68799/"}