Kernel crash via repeated team-port list deletion
Published Jan 13, 2026 · Updated Jan 13, 2026
Linux Kernel contains a team driver flaw that allows local users to crash the kernel through a crafted team-port priority update. After a queued team port is disabled and removed from qom_list, team_queue_override_port_prio_changed() wrongly deletes the same list entry again when its priority changes. Exploitation requires local low-privileged access to submit team generic-netlink options and a disabled port retaining a nonzero queue ID; the resulting list corruption triggers a kernel BUG and service interruption.
Summary
What happened
Linux Kernel contains a team driver flaw that allows local users to crash the kernel through a crafted team-port priority update. After a queued team port is disabled and removed from qom_list, team_queue_override_port_prio_changed() wrongly deletes the same list entry again when its priority changes. Exploitation requires local low-privileged access to submit team generic-netlink options and a disabled port retaining a nonzero queue ID; the resulting list corruption triggers a kernel BUG and service interruption.
The record
- CVE
- CVE-2025-71091
- Published
- Jan 13, 2026
- Updated
- Jan 13, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 13, 2026CVE publishedPublication date reported by the CVE source.
- Jan 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.11
- Affected versionversion=6c31ff366c1116823e77019bae3e92e9d77a49f4 <107d245f84cb4f55f597d31eda34b42a2b7d6952
- Affected versionversion=6c31ff366c1116823e77019bae3e92e9d77a49f4 <53a727a8bfd78c739e130a781192d0f6f8e03d39
- Affected versionversion=6c31ff366c1116823e77019bae3e92e9d77a49f4 <6bfb62b6010a16112dcae52f490e5e0e6abe12a3
- Affected versionversion=6c31ff366c1116823e77019bae3e92e9d77a49f4 <932ac51d9953eaf77a1252f79b656d4ca86163c6
- Affected versionversion=6c31ff366c1116823e77019bae3e92e9d77a49f4 <b71187648ef2349254673d0523fdf96d1fe3d758
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo