In the Linux kernel, the following vulnerability has been resolved:
openvswitch: validate MPLS set/set_masked payload length
validate_set() accepted OVS_KEY_ATTR_MPLS as variable-sized payload for
SET/SET_MASKED actions. In action handling, OVS expects fixed-size
MPLS key data (struct ovs_key_mpls).
Use the already normalized key_len (masked case included) and reject
non-matching MPLS action key sizes.
Reject invalid MPLS action payload lengths early.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux kernel’s Open vSwitch component allowed malformed MPLS action data to pass validation even though later processing expected a fixed-size structure. A local, low-privileged attacker could potentially cause serious confidentiality loss or system disruption. The published CVSS score is 7.1.
Executive priority
Prioritize exposed multi-user, virtualization, container, and software-defined networking hosts using kernel Open vSwitch. Treat remediation as high priority, but verify vendor package status before emergency action because the supplied affected-version mapping is unclear and no active exploitation is documented.
Technical view
Open vSwitch validation treated OVS_KEY_ATTR_MPLS payloads for SET and SET_MASKED actions as variable length. Subsequent action handling expected struct ovs_key_mpls, creating unsafe processing when lengths differed. The kernel fix uses the normalized key length, including masked actions, and rejects invalid MPLS payload sizes before action handling.
Likely exposure
Exposure is most plausible on affected Linux systems using the kernel Open vSwitch datapath, particularly where local low-privileged users or processes can reach relevant OVS action interfaces. The supplied version data is ambiguous and includes duplicated commit identifiers, so distribution-specific package status should determine actual exposure.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction, with potentially high confidentiality and availability impact. The source bundle says this CVE is not in KEV and provides no evidence of active exploitation or a public exploit.
Researcher notes
The record provides no CWE and does not describe the precise memory-safety failure or observed crash behavior. Multiple stable-kernel commits are referenced, apparently covering supported branches. The affected-version data contains unusual entries and repeated hashes; researchers should rely on branch-specific commits and vendor backport records rather than raw version strings alone.
Mitigation direction
Install a vendor kernel update containing the applicable referenced stable fix.
Reboot into the updated kernel and confirm the running version changed.
Check distribution security guidance for backport status and affected package versions.
Where operationally feasible, reduce local access to systems using kernel Open vSwitch.
Validation and detection
Inventory systems loading or using the kernel Open vSwitch datapath.
Record running kernel versions and distribution package release identifiers.
Compare each package against vendor advisories or documented backported fix commits.
Confirm the updated kernel is active after reboot, not merely installed.
Review monitoring for unusual local crashes or OVS-related kernel faults.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-31679 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.