Linux: Access of Resource Using Incompatible Type
CVE-2026-31502 is a high-severity access of resource using incompatible type vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions c6e255b0ce30cdea37e34d6d87e2212eb8c7f7a4, 420e5aad7ba89e8f79e2dc8327b0c0c24c1c1d53, 6d3161fa3eee64d46b766fb0db33ec7f300ef52d as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.13% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to c6e255b0ce30cdea37e34d6d87e2212eb8c7f7a4 or 420e5aad7ba89e8f79e2dc8327b0c0c24c1c1d53 or 6d3161fa3eee64d46b766fb0db33ec7f300ef52d or 0a7468ed49a6b65d34abcc6eb60e15f7f6d34da0, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.80 or 6.18.21 or 6.19.11, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 1d76efe1577b4323609b1bcbfafa8b731eda071a up to, but not including, c6e255b0ce30cdea37e34d6d87e2212eb8c7f7a4; 1d76efe1577b4323609b1bcbfafa8b731eda071a up to, but not including, 420e5aad7ba89e8f79e2dc8327b0c0c24c1c1d53; 1d76efe1577b4323609b1bcbfafa8b731eda071a up to, but not including, 6d3161fa3eee64d46b766fb0db33ec7f300ef52d; 1d76efe1577b4323609b1bcbfafa8b731eda071a up to, but not including, 0a7468ed49a6b65d34abcc6eb60e15f7f6d34da0; 1d76efe1577b4323609b1bcbfafa8b731eda071a up to, but not including, 20491d384d973a63fbdaf7a71e38d69b0659ea55; 1d76efe1577b4323609b1bcbfafa8b731eda071a up to, but not including, 425000dbf17373a4ab8be9428f5dc055ef870a56; 3.7 | c6e255b0ce30cdea37e34d6d87e2212eb8c7f7a4, 420e5aad7ba89e8f79e2dc8327b0c0c24c1c1d53, 6d3161fa3eee64d46b766fb0db33ec7f300ef52d, 0a7468ed49a6b65d34abcc6eb60e15f7f6d34da0, 20491d384d973a63fbdaf7a71e38d69b0659ea55, 425000dbf17373a4ab8be9428f5dc055ef870a56 |
| Linux | Linux Kernel | 3.7.1 up to, but not including, 6.12.80; 6.13 up to, but not including, 6.18.21; 6.19 up to, but not including, 6.19.11; 3.7; 7.0 | 6.12.80, 6.18.21, 6.19.11 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Access of Resource Using Incompatible Type
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
More Access of Resource Using Incompatible Type vulnerabilities (CWE-843)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Recent Access of Resource Using Incompatible Type vulnerabilities
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 7.8 High severity
- 7.7 High severity
- 9.8 Critical severity
Spotted an error? Tell us.