Skip to main content
VulnerabilityPublished Updated

CVE-2025-68816: Linux kernel · net/mlx5: fw_tracer, Validate format string parameters

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in b35966042d20b14e2d83330049f77deec5229749 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:42 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-16.

Patch
Available – fixed in b35966042d20b14e2d83330049f77deec5229749, 95624b731c490a4b849844269193a233d6d556a0, 768d559f466cdd72849110a7ecd76a21d52dcfe3 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 70dd6fdb8987b14f7b6105f6be0617299e459398, < b35966042d20b14e2d83330049f77deec5229749
Fixed in
  • b35966042d20b14e2d83330049f77deec5229749
LinuxLinuxAffected
  • ≥ 70dd6fdb8987b14f7b6105f6be0617299e459398, < 95624b731c490a4b849844269193a233d6d556a0
Fixed in
  • 95624b731c490a4b849844269193a233d6d556a0
LinuxLinuxAffected
  • ≥ 70dd6fdb8987b14f7b6105f6be0617299e459398, < 768d559f466cdd72849110a7ecd76a21d52dcfe3
Fixed in
  • 768d559f466cdd72849110a7ecd76a21d52dcfe3
LinuxLinuxAffected
  • ≥ 70dd6fdb8987b14f7b6105f6be0617299e459398, < 45bd283b1d69e2c97cddcb9956f0e0261fc4efd7
Fixed in
  • 45bd283b1d69e2c97cddcb9956f0e0261fc4efd7
LinuxLinuxAffected
  • ≥ 70dd6fdb8987b14f7b6105f6be0617299e459398, < 38ac688b52ef26a88f8bc4fe26d24fdd0ff91e5d
Fixed in
  • 38ac688b52ef26a88f8bc4fe26d24fdd0ff91e5d
LinuxLinuxAffected
  • ≥ 70dd6fdb8987b14f7b6105f6be0617299e459398, < 8c35c2448086870509ede43947845be0833251f0
Fixed in
  • 8c35c2448086870509ede43947845be0833251f0

Description

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: fw_tracer, Validate format string parameters Add validation for format string parameters in the firmware tracer to prevent potential security vulnerabilities and crashes from malformed format strings received from firmware. The firmware tracer receives format strings from the device firmware and uses them to format trace messages. Without proper validation, bad firmware could provide format strings with invalid format specifiers (e.g., %s, %p, %n) that could lead to crashes, or other undefined behavior. Add mlx5_tracer_validate_params() to validate that all format specifiers in trace strings are limited to safe integer/hex formats (%x, %d, %i, %u, %llx, %lx, etc.). Reject strings containing other format types that could be used to access arbitrary memory or cause crashes. Invalid format strings are added to the trace output for visibility with "BAD_FORMAT: " prefix.

References

Community reviews

Loading reviews…