CVE-2025-71091
Description
A list corruption vulnerability was found in the Linux kernel's network team driver. When a port is disabled and later has its priority changed, team_queue_override_port_prio_changed() incorrectly attempts to delete the port from a list it was already removed from during disable. This triggers a list_del corruption BUG when the function tries to remove an entry with LIST_POISON2 as its prev pointer.
Statement
This vulnerability can be triggered through netlink operations on team network interfaces. An unprivileged user with network namespace capabilities could potentially trigger this crash by manipulating team port priorities after disabling ports. The impact is limited to denial of service through a kernel BUG crash.
Mitigation
To mitigate this issue, prevent the team module from being loaded if network teaming is not required. See https://access.redhat.com/solutions/41278 for instructions on how to blacklist a kernel module.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | 7.8 | N/A |
| Attack Vector | Local | Local | N/A |
| Attack Complexity | Low | Low | N/A |
| Privileges Required | Low | Low | N/A |
| User Interaction | None | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | None | High | N/A |
| Integrity Impact | None | High | N/A |
| Availability Impact | High | High | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Availability,Integrity
Technical Impact: DoS: Crash, Exit, or Restart
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
