CVE-2025-40254: net: openvswitch: remove never-working support for setting nsh fields
Noroxi assessment
Priority: Monitor (action score 0/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.25% (FIRST EPSS).
- Fixed version: Linux Linux 0b903f33c31c82b1c3591279fd8a23893802b987, 3415faa1fcb4150f29a72c5ecf959339d797feb7, 3d2e7d3b28469081ccf08301df07cc411a1cc5e9; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1.
Low priority for now. Upgrade to Linux Linux 0b903f33c31c82b1c3591279fd8a23893802b987, 3415faa1fcb4150f29a72c5ecf959339d797feb7, 3d2e7d3b28469081ccf08301df07cc411a1cc5e9; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1 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: net: openvswitch: remove never-working support for setting nsh fields The validation of the set(nsh(...)) action is completely wrong. It runs through the nsh_key_put_from_nlattr() function that is the same function that validates NSH keys for the flow match and the push_nsh() action. However, the set(nsh(...)) has a very different memory layout. Nested attributes in there are doubled in size in case of the masked set(). That makes proper validation impossible. There is also confusion in the code between the 'masked' flag, that says that the nested attributes are doubled in size containing both the value and the mask, and the 'is_mask' that says that the value we're parsing is the mask. This is causing kernel crash on trying to write into mask part of the match with SW_FLOW_KEY_PUT() during validation, while validate_nsh() doesn't allocate any memory for it: BUG: kernel NULL pointer dereference, address: 0000000000000018 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 1c2383067 P4D 1c2383067 PUD 20b703067 PMD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 8 UID: 0 Kdump: loaded Not tainted 6.17.0-rc4+ #107 PREEMPT(voluntary) RIP: 0010:nsh_key_put_from_nlattr+0x19d/0x610 [openvswitch] Call Trace: <TASK> validate_nsh+0x60/0x90 [openvswitch] validate_set.constprop.0+0x270/0x3c0 [openvswitch] __ovs_nla_copy_actions+0x477/0x860 [openvswitch] ovs_nla_copy_actions+0x8d/0x100 [openvswitch] ovs_packet_cmd_execute+0x1cc/0x310 [openvswitch] genl_family_rcv_msg_doit+0xdb/0x130 genl_family_rcv_msg+0x14b/0x220 genl_rcv_msg+0x47/0xa0 netlink_rcv_skb+0x53/0x100 genl_rcv+0x24/0x40 netlink_unicast+0x280/0x3b0 netlink_sendmsg+0x1f7/0x430 ____sys_sendmsg+0x36b/0x3a0 ___sys_sendmsg+0x87/0xd0 __sys_sendmsg+0x6d/0xd0 do_syscall_64+0x7b/0x2c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The third issue with this process is that while trying to convert the non-masked set into masked one, validate_set() copies and doubles the size of the OVS_KEY_ATTR_NSH as if it didn't have any nested attributes. It should be copying each nested attribute and doubling them in size independently. And the process must be properly reversed during the conversion back from masked to a non-masked variant during the flow dump. In the end, the only two outcomes of trying to use this action are either validation failure or a kernel crash. And if somehow someone manages to install a flow with such an action, it will most definitely not do what it is supposed to, since all the keys and the masks are mixed up. Fixing all the issues is a complex task as it requires re-writing most of the validation code. Given that and the fact that this functionality never worked since introduction, let's just remove it altogether. It's better to re-introduce it later with a proper implementation instead of trying to fix it in stable releases.
- Published
- Dec 4, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
—
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
- 4.15affected
- b2d0f5d5dc53532e6f07bc546a476a55ebdfe0f3 and later · before 3415faa1fcb4150f29a72c5ecf959339d797feb7affected · git
- b2d0f5d5dc53532e6f07bc546a476a55ebdfe0f3 and later · before 3d2e7d3b28469081ccf08301df07cc411a1cc5e9affected · git
- b2d0f5d5dc53532e6f07bc546a476a55ebdfe0f3 and later · before f95bef5ba0b88d971b02c776f24bd17544930a3aaffected · git
- b2d0f5d5dc53532e6f07bc546a476a55ebdfe0f3 and later · before 87d2429381ddcf8cbd30c8c36793a4f7916d5f99affected · git
- b2d0f5d5dc53532e6f07bc546a476a55ebdfe0f3 and later · before 0b903f33c31c82b1c3591279fd8a23893802b987affected · git
- b2d0f5d5dc53532e6f07bc546a476a55ebdfe0f3 and later · before 9c61d8fe1350b7322f4953318165d6719c3b1475affected · git
- b2d0f5d5dc53532e6f07bc546a476a55ebdfe0f3 and later · before 4689ba45296dbb3a47e70a1bc2ed0328263e48f3affected · git
- b2d0f5d5dc53532e6f07bc546a476a55ebdfe0f3 and later · before dfe28c4167a9259fc0c372d9f9473e1ac95cff67affected · git
- before 4.15not 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:11 | linux-6.1 | before 6.1.159-1~deb11u1 | 6.1.159-1~deb11u1 |
| Debian:12 | linux | before 6.1.159-1 | 6.1.159-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.10-1 | 6.17.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40252Dec 4, 2025 · net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()39Monitor
- ← EarlierCVE-2025-40253Dec 4, 2025 · s390/ctcm: Fix double-kfree35Monitor
- Later →CVE-2025-40255Dec 4, 2025 · net: core: prevent NULL deref in generic_hwtstamp_ioctl_lower()0Monitor
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 | 0b903f33c31c82b1c3591279fd8a23893802b987 | Vendor (CNA) |
| Linux Linux | 3415faa1fcb4150f29a72c5ecf959339d797feb7 | Vendor (CNA) |
| Linux Linux | 3d2e7d3b28469081ccf08301df07cc411a1cc5e9 | Vendor (CNA) |
| Linux Linux | 4689ba45296dbb3a47e70a1bc2ed0328263e48f3 | Vendor (CNA) |
| Linux Linux | 87d2429381ddcf8cbd30c8c36793a4f7916d5f99 | Vendor (CNA) |
| Linux Linux | 9c61d8fe1350b7322f4953318165d6719c3b1475 | Vendor (CNA) |
| Linux Linux | dfe28c4167a9259fc0c372d9f9473e1ac95cff67 | Vendor (CNA) |
| Linux Linux | f95bef5ba0b88d971b02c776f24bd17544930a3a | Vendor (CNA) |
| azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 | 6.6.119.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.159-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.159-1~deb11u1 · Debian:11 | Package registry (OSV) |
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.
No nightly-computed relations.
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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/3415faa1fcb4150f29a72c5ecf959339d797feb7
- git.kernel.org/stable/c/3d2e7d3b28469081ccf08301df07cc411a1cc5e9
- git.kernel.org/stable/c/4689ba45296dbb3a47e70a1bc2ed0328263e48f3
- git.kernel.org/stable/c/87d2429381ddcf8cbd30c8c36793a4f7916d5f99
- git.kernel.org/stable/c/9c61d8fe1350b7322f4953318165d6719c3b1475
- git.kernel.org/stable/c/dfe28c4167a9259fc0c372d9f9473e1ac95cff67
- git.kernel.org/stable/c/f95bef5ba0b88d971b02c776f24bd17544930a3a
- cert-portal.siemens.com/productcert/html/ssa-253495.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.