CVE-2026-31502: team: fix header_ops type confusion with non-Ethernet ports
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0a7468ed49a6b65d34abcc6eb60e15f7f6d34da0, 20491d384d973a63fbdaf7a71e38d69b0659ea55, 420e5aad7ba89e8f79e2dc8327b0c0c24c1c1d53.
Low priority for now. Upgrade to Linux Linux 0a7468ed49a6b65d34abcc6eb60e15f7f6d34da0, 20491d384d973a63fbdaf7a71e38d69b0659ea55, 420e5aad7ba89e8f79e2dc8327b0c0c24c1c1d53 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2026-12538
- openSUSE-SU-2026:21388-1
- SUSE-SU-2026:22521-1
- SUSE-SU-2026:22522-1
- SUSE-SU-2026:22665-1
- SUSE-SU-2026:22666-1
- SUSE-SU-2026:22742-1
- SUSE-SU-2026:22769-1
- SUSE-SU-2026:22812-1
- SUSE-SU-2026:22835-1
- SUSE-SU-2026:2799-1
- SUSE-SU-2026:2800-1
- SUSE-SU-2026:2914-1
- SUSE-SU-2026:4279-1
- SUSE-SU-2026:4284-1
- SUSE-SU-2026:4347-1
- SUSE-SU-2026:4369-1
- SUSE-SU-2026:4595-1
- Published
- Apr 22, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-843
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.7.1 and later · before 6.12.80
- linux linux kernel6.13 and later · before 6.18.21
- linux linux kernel6.19 and later · before 6.19.11
- linux linux kernel3.7
- linux linux kernel7.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.7affected
- 1d76efe1577b4323609b1bcbfafa8b731eda071a and later · before c6e255b0ce30cdea37e34d6d87e2212eb8c7f7a4affected · git
- 1d76efe1577b4323609b1bcbfafa8b731eda071a and later · before 420e5aad7ba89e8f79e2dc8327b0c0c24c1c1d53affected · git
- 1d76efe1577b4323609b1bcbfafa8b731eda071a and later · before 6d3161fa3eee64d46b766fb0db33ec7f300ef52daffected · git
- 1d76efe1577b4323609b1bcbfafa8b731eda071a and later · before 0a7468ed49a6b65d34abcc6eb60e15f7f6d34da0affected · git
- 1d76efe1577b4323609b1bcbfafa8b731eda071a and later · before 20491d384d973a63fbdaf7a71e38d69b0659ea55affected · git
- 1d76efe1577b4323609b1bcbfafa8b731eda071a and later · before 425000dbf17373a4ab8be9428f5dc055ef870a56affected · git
- before 3.7not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.145 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.11-1 | 6.19.11-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.36.1 | 6.12.0-160000.36.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.36.1 | 6.12.0-160000.36.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.36.1 | 6.12.0-160000.36.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.36.1 | 6.12.0-160000.36.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.36.1.160000.2.17 | 6.12.0-160000.36.1.160000.2.17 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.36.1 | 6.12.0-160000.36.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.36.1 | 6.12.0-160000.36.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.36.1 | 6.12.0-160000.36.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.36.1 | 6.12.0-160000.36.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.36.1 | 6.12.0-160000.36.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.36.1 | 6.12.0-160000.36.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.36.1 | 6.12.0-160000.36.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.36.1 | 6.12.0-160000.36.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-64kb | before 5.14.21-150400.24.240.2 | 5.14.21-150400.24.240.2 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-docs | before 5.14.21-150400.24.240.1 | 5.14.21-150400.24.240.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-obs-build | before 5.14.21-150400.24.240.1 | 5.14.21-150400.24.240.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-syms | before 5.14.21-150400.24.240.1 | 5.14.21-150400.24.240.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-64kb | before 5.14.21-150500.55.189.1 | 5.14.21-150500.55.189.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-docs | before 5.14.21-150500.55.189.1 | 5.14.21-150500.55.189.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-obs-build | before 5.14.21-150500.55.189.1 | 5.14.21-150500.55.189.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-syms | before 5.14.21-150500.55.189.1 | 5.14.21-150500.55.189.1 |
+58
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-31500Apr 22, 2026 · Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock31Monitor
- ← EarlierCVE-2026-31501Apr 22, 2026 · net: ti: icssg-prueth: fix use-after-free of CPPI descriptor in RX path39Monitor
- Later →CVE-2026-31503Apr 22, 2026 · udp: Fix wildcard bind conflict check when using hash222Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0a7468ed49a6b65d34abcc6eb60e15f7f6d34da0 | Vendor (CNA) |
| Linux Linux | 20491d384d973a63fbdaf7a71e38d69b0659ea55 | Vendor (CNA) |
| Linux Linux | 420e5aad7ba89e8f79e2dc8327b0c0c24c1c1d53 | Vendor (CNA) |
| Linux Linux | 425000dbf17373a4ab8be9428f5dc055ef870a56 | Vendor (CNA) |
| Linux Linux | 6d3161fa3eee64d46b766fb0db33ec7f300ef52d | Vendor (CNA) |
| Linux Linux | c6e255b0ce30cdea37e34d6d87e2212eb8c7f7a4 | Vendor (CNA) |
| debian:linux | 6.12.85-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.36.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.36.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.36.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.36.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.36.1.160000.2.17 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.36.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.36.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.36.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.36.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.36.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.36.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.36.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.36.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-azure | 6.12.0-160000.36.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-49.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.36.1.160000.2.17 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.36.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.4.0-49.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.36.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-obs-qa | 6.12.0-160000.36.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-49.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-49.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-49.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
+1
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-4306213 days apartBluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp()28Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-843 · Access of Resource Using Incompatible Type ('Type Confusion')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/20491d384d973a63fbdaf7a71e38d69b0659ea55
- git.kernel.org/stable/c/420e5aad7ba89e8f79e2dc8327b0c0c24c1c1d53
- git.kernel.org/stable/c/425000dbf17373a4ab8be9428f5dc055ef870a56
- git.kernel.org/stable/c/6d3161fa3eee64d46b766fb0db33ec7f300ef52d
- git.kernel.org/stable/c/c6e255b0ce30cdea37e34d6d87e2212eb8c7f7a4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.