CVE-2026-31502

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

team: fix header_ops type confusion with non-Ethernet ports

Similar to commit 950803f72547 ("bonding: fix type confusion in bond_setup_by_slave()") team has the same class of header_ops type confusion.

For non-Ethernet ports, team_setup_by_port() copies port_dev->header_ops directly. When the team device later calls dev_hard_header() or dev_parse_header(), these callbacks can run with the team net_device instead of the real lower device, so netdev_priv(dev) is interpreted as the wrong private type and can crash.

The syzbot report shows a crash in bond_header_create(), but the root cause is in team: the topology is gre -> bond -> team, and team calls the inherited header_ops with its own net_device instead of the lower device, so bond_header_create() receives a team device and interprets netdev_priv() as bonding private data, causing a type confusion crash.

Fix this by introducing team header_ops wrappers for create/parse, selecting a team port under RCU, and calling the lower device callbacks with port->dev, so each callback always sees the correct net_device context.

Also pass the selected lower device to the lower parse callback, so recursion is bounded in stacked non-Ethernet topologies and parse callbacks always run with the correct device context.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 22, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

team: fix header_ops type confusion with non-Ethernet ports - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6d3161fa3eee64d46b766fb0db33ec7f300ef52d
generic

team: fix header_ops type confusion with non-Ethernet ports - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/425000dbf17373a4ab8be9428f5dc055ef870a56
generic

team: fix header_ops type confusion with non-Ethernet ports - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/20491d384d973a63fbdaf7a71e38d69b0659ea55
generic

team: fix header_ops type confusion with non-Ethernet ports - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0a7468ed49a6b65d34abcc6eb60e15f7f6d34da0

Vendor Advisories for CVE-2026-31502(2)

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

Patch Availability(12)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1

Weakness Classification(1)

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

All Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 5× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 230 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31502?
CVE-2026-31502 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: team: fix header_ops type confusion with non-Ethernet ports Similar to commit 950803f72547 ("bonding: fix type confusion in bondsetupbyslave()") team has the same class of headerops type confusion. For non-Ethernet ports,…
When was CVE-2026-31502 disclosed?
CVE-2026-31502 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31502 actively exploited?
CVE-2026-31502 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-31502?
CVE-2026-31502 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31502?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31502, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31502

Explore →

Is Your Infrastructure Affected by CVE-2026-31502?

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