CVE-2025-71091
BaseFortify
Publication date: 2026-01-13
Last updated on: 2026-03-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.11 (inc) to 5.15.198 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.4 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.160 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.120 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.64 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 3.11.1 (inc) to 5.10.248 (exc) |
| linux | linux_kernel | 3.11 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves a bug in the team_queue_override_port_prio_changed() function. When a network port is disabled but still has a non-zero queue_id, the function incorrectly attempts to remove the port from a list it is no longer part of, causing a kernel BUG due to list corruption. The issue arises because the function does not properly check if the port is enabled before attempting to delete it from the list, leading to invalid memory operations and kernel crashes.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash due to invalid memory operations when handling network port priority changes. This can lead to system instability, denial of service, and potential disruption of network operations on affected systems.
What immediate steps should I take to mitigate this vulnerability?
Update the Linux kernel to a version that includes the fix for this vulnerability, which changes the check in team_queue_override_port_prio_changed() to return early if the port is not enabled, preventing the BUG. Until then, avoid using the affected team networking features that trigger this bug.