BaseFortify

Publication date: 2025-12-16

Last updated on: 2025-12-18

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: udp_tunnel: use netdev_warn() instead of netdev_WARN() netdev_WARN() uses WARN/WARN_ON to print a backtrace along with file and line information. In this case, udp_tunnel_nic_register() returning an error is just a failed operation, not a kernel bug. udp_tunnel_nic_register() can fail due to a memory allocation failure (kzalloc() or udp_tunnel_nic_alloc()). This is a normal runtime error and not a kernel bug. Replace netdev_WARN() with netdev_warn() accordingly.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-12-16

Last Modified

2025-12-18

Generated

2026-07-06

AI Q&A

2025-12-16

EPSS Evaluated

2026-07-05

NVD

CVE-2025-68191

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability involves the Linux kernel's udp_tunnel component using netdev_WARN(), which triggers a kernel warning with a backtrace when udp_tunnel_nic_register() fails. However, such failure is a normal runtime error (like memory allocation failure) and not a kernel bug. The fix replaces netdev_WARN() with netdev_warn() to avoid unnecessary kernel warnings for expected errors.

Impact Analysis

The impact is that the Linux kernel might produce unnecessary kernel warnings and backtraces for normal runtime errors in udp_tunnel_nic_register(), which could cause confusion or noise in system logs but does not indicate a kernel bug or cause a system failure.

Mitigation Strategies

Update the Linux kernel to a version where the udp_tunnel component uses netdev_warn() instead of netdev_WARN(), as this change addresses the issue by preventing unnecessary kernel warnings caused by normal runtime errors. This involves applying the patch or upgrading to the fixed kernel release.

Hi! I’m here to help you understand CVE-2025-68191. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70