CVE-2025-71091

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-01-13. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-2256 (ENISA EUVD) · GHSA-34rx-7455-xg2h (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

team: fix check for port enabled in team_queue_override_port_prio_changed()

There has been a syzkaller bug reported recently with the following trace:

list_del corruption, ffff888058bea080->prev is LIST_POISON2 (dead000000000122) ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:59! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 3 UID: 0 PID: 21246 Comm: syz.0.2928 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:__list_del_entry_valid_or_report+0x13e/0x200 lib/list_debug.c:59 Code: 48 c7 c7 e0 71 f0 8b e8 30 08 ef fc 90 0f 0b 48 89 ef e8 a5 02 55 fd 48 89 ea 48 89 de 48 c7 c7 40 72 f0 8b e8 13 08 ef fc 90 <0f> 0b 48 89 ef e8 88 02 55 fd 48 89 ea 48 b8 00 00 00 00 00 fc ff RSP: 0018:ffffc9000d49f370 EFLAGS: 00010286 RAX: 000000000000004e RBX: ffff888058bea080 RCX: ffffc9002817d000 RDX: 0000000000000000 RSI: ffffffff819becc6 RDI: 0000000000000005 RBP: dead000000000122 R08: 0000000000000005 R09: 0000000000000000 R10: 0000000080000000 R11: 0000000000000001 R12: ffff888039e9c230 R13: ffff888058bea088 R14: ffff888058bea080 R15: ffff888055461480 FS: 00007fbbcfe6f6c0(0000) GS:ffff8880d6d0a000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c3afcb0 CR3: 00000000382c7000 CR4: 0000000000352ef0 Call Trace: __list_del_entry_valid include/linux/list.h:132 [inline] __list_del_entry include/linux/list.h:223 [inline] list_del_rcu include/linux/rculist.h:178 [inline] __team_queue_override_port_del drivers/net/team/team_core.c:826 [inline] __team_queue_override_port_del drivers/net/team/team_core.c:821 [inline] team_queue_override_port_prio_changed drivers/net/team/team_core.c:883 [inline] team_priority_option_set+0x171/0x2f0 drivers/net/team/team_core.c:1534 team_option_set drivers/net/team/team_core.c:376 [inline] team_nl_options_set_doit+0x8ae/0xe60 drivers/net/team/team_core.c:2653 genl_family_rcv_msg_doit+0x209/0x2f0 net/netlink/genetlink.c:1115 genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline] genl_rcv_msg+0x55c/0x800 net/netlink/genetlink.c:1210 netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552 genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219 netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline] netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1346 netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1896 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg net/socket.c:742 [inline] ____sys_sendmsg+0xa98/0xc70 net/socket.c:2630 ___sys_sendmsg+0x134/0x1d0 net/socket.c:2684 __sys_sendmsg+0x16d/0x220 net/socket.c:2716 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f

The problem is in this flow: 1) Port is enabled, queue_id != 0, in qom_list 2) Port gets disabled -> team_port_disable() -> team_queue_override_port_del() -> del (removed from list) 3) Port is disabled, queue_id != 0, not in any list 4) Priority changes -> team_queue_override_port_prio_changed() -> checks: port disabled && queue_id != 0 -> calls del - hits the BUG as it is removed already

To fix this, change the check in team_queue_override_port_prio_changed() so it returns early if port is not enabled.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 13, 2026

Last Modified

October 19, 2026

Advisory Details (7)

Auto-updated Aug 3, 2026
Patch available.
Web page

team: fix check for port enabled in team_queue_override_port_prio_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f820e438b8ec2a8354e70e75145f05fe45500d97
Web page

team: fix check for port enabled in team_queue_override_port_prio_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b71187648ef2349254673d0523fdf96d1fe3d758
Web page

team: fix check for port enabled in team_queue_override_port_prio_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/932ac51d9953eaf77a1252f79b656d4ca86163c6
Web page

team: fix check for port enabled in team_queue_override_port_prio_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6bfb62b6010a16112dcae52f490e5e0e6abe12a3
Web page

team: fix check for port enabled in team_queue_override_port_prio_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/53a727a8bfd78c739e130a781192d0f6f8e03d39
Web page

team: fix check for port enabled in team_queue_override_port_prio_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25029e813c4aae5fcf7118e8dd5c56e382b9a1a3
Web page

team: fix check for port enabled in team_queue_override_port_prio_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/107d245f84cb4f55f597d31eda34b42a2b7d6952

Vendor Advisories for CVE-2025-71091(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gke-5.15 (5.15.0.1099.98) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-22.22) @ questing2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1103.93) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-10-27ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1094.98) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1044.46) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1051.54) @ noble2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-110.110) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1012.12) @ questing2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1010.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1011.11) @ questing2026-10-27ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1013.13) @ questing2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2042.43) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1051.54.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1052.56) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1049.50~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1054.57~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1047.48) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1014.14) @ questing2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1054.60) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1054.60+fips1) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1022.22) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1054.57+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-10-27ubuntu
linuxKernel @ 5.10.248 (fixes >=3.11.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (48 versions)
  • every version up to 5.10.249-1: fixed in 5.10.249-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.159-1~deb11u1 (14 versions)
  • every version up to 6.1.162-1~deb11u1: fixed in 6.1.162-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)
  • every version up to 6.1.162-1: fixed in 6.1.162-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)
  • every version up to 6.12.69-1: fixed in 6.12.69-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (95 versions)
  • every version up to 6.18.5-1: fixed in 6.18.5-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 205 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 106 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-27 18:25 UTCEG score recompute
  7. 2026-10-27 18:25 UTCVendor advisory
  8. 2026-10-27 18:24 UTCGHSA enrichmentGHSA-34rx-7455-xg2h · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-25 16:02 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-19 19:33 UTCVendor advisory
  19. 2026-10-19 19:32 UTCGHSA enrichmentGHSA-34rx-7455-xg2h · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-19 18:30 UTCEG score recompute
  21. 2026-10-19 18:30 UTCVendor advisory
  22. 2026-10-19 18:29 UTCGHSA enrichmentGHSA-34rx-7455-xg2h · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-18 05:16 UTCEG score recompute
Show 74 more
  1. 2026-10-17 21:52 UTCEG score recompute
  2. 2026-10-17 21:52 UTCVendor advisory
  3. 2026-10-17 21:52 UTCGHSA enrichmentGHSA-34rx-7455-xg2h · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-12 16:45 UTCEG score recompute
  9. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-11 20:20 UTCEG score recompute
  11. 2026-10-11 18:32 UTCEG score recompute
  12. 2026-10-11 15:07 UTCEG score recompute
  13. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-08 21:58 UTCOSV refresh
  16. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  28. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  29. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  30. 2026-09-19 04:36 UTCOSV refresh
  31. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  32. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  33. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  34. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  35. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  36. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  37. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  38. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  39. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  40. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  43. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  45. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-08-31 08:25 UTCOSV refresh
  47. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  49. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  50. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  51. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  52. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  53. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  54. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  55. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  56. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  57. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  58. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  59. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  60. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  61. 2026-08-14 14:40 UTCEG score recompute
  62. 2026-08-14 14:40 UTCVendor advisory
  63. 2026-08-14 14:40 UTCGHSA enrichmentGHSA-34rx-7455-xg2h · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  65. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  66. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  67. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  68. 2026-08-09 20:11 UTCEG score recompute
  69. 2026-08-09 20:11 UTCVendor advisory
  70. 2026-08-09 20:11 UTCGHSA enrichmentGHSA-34rx-7455-xg2h · GitHub severity HIGH · GitHub CVSS 7.8
  71. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  72. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  73. 2026-08-08 00:54 UTCEG score recompute
  74. 2026-08-08 00:54 UTCVendor advisory

Frequently asked(5)

What is CVE-2025-71091?
CVE-2025-71091 is a high-severity vulnerability; its CVE record was published on January 13, 2026. In the Linux kernel, the following vulnerability has been resolved: team: fix check for port enabled in team_queue_override_port_prio_changed() There has been a syzkaller bug reported recently with the following trace: list_del corruption, ffff888058bea080->prev is LIST_POISON2 (dead000000000122)…
When was the CVE record for CVE-2025-71091 published?
The CVE record for CVE-2025-71091 was published on January 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-71091 actively exploited?
CVE-2025-71091 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-71091?
CVE-2025-71091 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-71091?
A fix for CVE-2025-71091 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-71091 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71091

Explore →

Is Your Infrastructure Affected by CVE-2025-71091?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.