{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68816 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68816 is a memory corruption 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-68816 and fix it if it is affected.\n\nWhat it is: CVE-2025-68816 is a memory corruption 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-68816 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-68816/ (Markdown: https://insights.sbomify.com/CVE-2025-68816/index.md)","id":"CVE-2025-68816","markdown":"https://insights.sbomify.com/CVE-2025-68816/index.md","name":"CVE-2025-68816","record":{"aliases":["AZL-74430","BELL-CVE-2025-68816","DEBIAN-CVE-2025-68816","GHSA-446v-vm34-72r6","ROOT-OS-DEBIAN-11-CVE-2025-68816","ROOT-OS-DEBIAN-12-CVE-2025-68816","ROOT-OS-DEBIAN-13-CVE-2025-68816","ROOT-OS-UBUNTU-2204-CVE-2025-68816","ROOT-OS-UBUNTU-2404-CVE-2025-68816","UBUNTU-CVE-2025-68816"],"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 driver","requires_auth":"none","summary":"Malicious firmware can send unsafe format strings to the mlx5 tracer, causing kernel crashes or potential code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[{"id":"CWE-134","name":"Use of Externally-Controlled Format String"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\"BAD_FORMAT: \" prefix.","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":"net/mlx5: fw_tracer, Validate format string parameters","id":"CVE-2025-68816","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"ksmbd: fix use-after-free in ksmbd_tree_connect_put under concurrency","id":"CVE-2025-68817"},"packages":[],"prev":{"headline":"net/sched: ets: Remove drr class from the active list if it changes to strict","id":"CVE-2025-68815"},"products":["Linux"],"published":"2026-01-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"Malicious firmware can send unsafe format strings to the mlx5 tracer, causing kernel crashes or potential code execution.","url":"https://insights.sbomify.com/CVE-2025-68816/"}