How to Fix CVE-2026-31679: openvswitch: validate MPLS set/set_masked payload length in Linux

By Sai Kiran Pandrala

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2026-31465: writeback: don't block sync for filesystems with no data integrity guarantees — writeback: don't block sync for filesystems with no data integrity guarantees
• How to Fix CVE-2026-43101: Security Vulnerability in Linux — Security Vulnerability in Linux
• How to Fix CVE-2026-43376: Use-After-Free in Linux , Use-After-Free in Linux
• How to Fix CVE-2026-23311: Critical Vulnerability in Linux , Critical Vulnerability in Linux
• How to Fix CVE-2026-23300: Critical Vulnerability in Linux , Critical Vulnerability in Linux

Last verified: 2026-05-25

CVE-2026-31679 is a openvswitch: validate mpls set/set_masked payload length in Linux Linux. Fix it by upgrading to 5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21.

What is CVE-2026-31679?

CVE-2026-31679 is a openvswitch: validate mpls set/set_masked payload length flaw in Linux Linux. It carries a CVSS base score of 7.1 (high). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: 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.

Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of Linux matches a version listed in the Affected row above.

# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux

How to fix CVE-2026-31679

Apply the vendor patch. Target the build named in the Fixed in row above (5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21). The runnable command set below covers the most common deployment patterns for Linux.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade linux
dpkg -s linux | grep Version

RHEL / CentOS / Rocky

sudo dnf upgrade linux -y
rpm -q linux

After applying the patch

1. Restart the service or device so the patched binary loads.
2. Confirm the running version matches the Fixed in row using the verification command below.
3. Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict network exposure

Block public access to the affected service at the perimeter. Allow only trusted source IPs.

# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4

# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
  -RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny"  -Direction Inbound -Action Block `
  -Protocol TCP -LocalPort 443

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux

Expected: a version at or above 5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21.

Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Is CVE-2026-31679 being exploited in the wild?

As of 2026-05-25, CVE-2026-31679 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.

What is the CVSS score for CVE-2026-31679?

The CVSS base score is 7.1 (High).

What version fixes this?

Upgrade to 5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21.

Will a WAF or IDS rule alone close this?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

References

• Official vendor advisory: https://git.kernel.org/stable/c/68f32ef0683c8d1c05cd2e4f16818fa63ff59c6f
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-31679
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://git.kernel.org/stable/c/4cae986225f8b8679ad86b924918e7d75a96aa61
• Additional reference: https://git.kernel.org/stable/c/8ed7b9930cbc3bc71f868fa79a68700ac88d586a
• Additional reference: https://git.kernel.org/stable/c/c1f97152df8dfb17e855ddf0fc409b7bd13e9700
• Additional reference: https://git.kernel.org/stable/c/98de18d327ef8cbbb704980e359e4872d8c28997

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*