openvswitch: cap upcall PID array size and pre-size vport replies
Noroxi assessment
Priority: Monitor (action score 22/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 1d6c02b86329883aa467a3a61f8d34369db73a2f, 2091c6aa0df6aba47deb5c8ab232b1cb60af3519, 8d59b80e69dddb665eb2de36e62859ab2073470e; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
Low priority for now. Upgrade to Linux Linux 1d6c02b86329883aa467a3a61f8d34369db73a2f, 2091c6aa0df6aba47deb5c8ab232b1cb60af3519, 8d59b80e69dddb665eb2de36e62859ab2073470e; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-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: openvswitch: cap upcall PID array size and pre-size vport replies The vport netlink reply helpers allocate a fixed-size skb with nlmsg_new(NLMSG_DEFAULT_SIZE, ...) but serialize the full upcall PID array via ovs_vport_get_upcall_portids(). Since ovs_vport_set_upcall_portids() accepts any non-zero multiple of sizeof(u32) with no upper bound, a CAP_NET_ADMIN user can install a PID array large enough to overflow the reply buffer, causing nla_put() to fail with -EMSGSIZE and hitting BUG_ON(err < 0). On systems with unprivileged user namespaces enabled (e.g., Ubuntu default), this is reachable via unshare -Urn since OVS vport mutation operations use GENL_UNS_ADMIN_PERM. kernel BUG at net/openvswitch/datapath.c:2414! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 1 UID: 0 PID: 65 Comm: poc Not tainted 7.0.0-rc7-00195-geb216e422044 #1 RIP: 0010:ovs_vport_cmd_set+0x34c/0x400 Call Trace: <TASK> genl_family_rcv_msg_doit (net/netlink/genetlink.c:1116) genl_rcv_msg (net/netlink/genetlink.c:1194) netlink_rcv_skb (net/netlink/af_netlink.c:2550) genl_rcv (net/netlink/genetlink.c:1219) netlink_unicast (net/netlink/af_netlink.c:1344) netlink_sendmsg (net/netlink/af_netlink.c:1894) __sys_sendto (net/socket.c:2206) __x64_sys_sendto (net/socket.c:2209) do_syscall_64 (arch/x86/entry/syscall_64.c:63) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) </TASK> Kernel panic - not syncing: Fatal exception Reject attempts to set more PIDs than nr_cpu_ids in ovs_vport_set_upcall_portids(), and pre-compute the worst-case reply size in ovs_vport_cmd_msg_size() based on that bound, similar to the existing ovs_dp_cmd_msg_size(). nr_cpu_ids matches the cap already used by the per-CPU dispatch configuration on the datapath side (ovs_dp_cmd_fill_info() serialises at most nr_cpu_ids PIDs), so the two sides stay consistent.
- Published
- May 27, 2026
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
| 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.17 and later · before 5.10.258
- linux linux kernel5.11 and later · before 5.15.209
- linux linux kernel5.16 and later · before 6.1.175
- linux linux kernel6.2 and later · before 6.6.141
- linux linux kernel6.7 and later · before 6.12.91
- linux linux kernel6.13 and later · before 6.18.33
- linux linux kernel6.19 and later · before 7.0.10
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.17affected
- 5cd667b0a4567048bb555927d6ee564f4e5620a9 and later · before 8d59b80e69dddb665eb2de36e62859ab2073470eaffected · git
- 5cd667b0a4567048bb555927d6ee564f4e5620a9 and later · before d9e47e29aacb9f8a9d59feb6ab5b128a9bbb40b0affected · git
- 5cd667b0a4567048bb555927d6ee564f4e5620a9 and later · before b39f763d720d623218bc1d95ace6855d7b474e81affected · git
- 5cd667b0a4567048bb555927d6ee564f4e5620a9 and later · before f9ef3db77a383d66847fd082c2b437d8ae4d9c63affected · git
- 5cd667b0a4567048bb555927d6ee564f4e5620a9 and later · before f99ac36b5d7c719d08a69fcdecce40f78a874e15affected · git
- 5cd667b0a4567048bb555927d6ee564f4e5620a9 and later · before fa6e90bc443bed8dc0d55bc5ea5b27ffdfe37704affected · git
- 5cd667b0a4567048bb555927d6ee564f4e5620a9 and later · before 1d6c02b86329883aa467a3a61f8d34369db73a2faffected · git
- 5cd667b0a4567048bb555927d6ee564f4e5620a9 and later · before 2091c6aa0df6aba47deb5c8ab232b1cb60af3519affected · git
- before 3.17not 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 | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.10-1 | 7.0.10-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.0.11-1.1 | 7.0.11-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2026-45838May 27, 2026 · bpf: fix end-of-list detection in cgroup_storage_get_next_key()22Monitor
- ← EarlierCVE-2026-45839May 27, 2026 · bpf: reject negative CO-RE accessor indices in bpf_core_parse_spec()31Monitor
- Later →CVE-2026-45841May 27, 2026 · netfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO22Monitor
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 | 1d6c02b86329883aa467a3a61f8d34369db73a2f | Vendor (CNA) |
| Linux Linux | 2091c6aa0df6aba47deb5c8ab232b1cb60af3519 | Vendor (CNA) |
| Linux Linux | 8d59b80e69dddb665eb2de36e62859ab2073470e | Vendor (CNA) |
| Linux Linux | b39f763d720d623218bc1d95ace6855d7b474e81 | Vendor (CNA) |
| Linux Linux | d9e47e29aacb9f8a9d59feb6ab5b128a9bbb40b0 | Vendor (CNA) |
| Linux Linux | f99ac36b5d7c719d08a69fcdecce40f78a874e15 | Vendor (CNA) |
| Linux Linux | f9ef3db77a383d66847fd082c2b437d8ae4d9c63 | Vendor (CNA) |
| Linux Linux | fa6e90bc443bed8dc0d55bc5ea5b27ffdfe37704 | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.141.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 7.0.11-1.1 · openSUSE:Tumbleweed | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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/2091c6aa0df6aba47deb5c8ab232b1cb60af3519
- git.kernel.org/stable/c/8d59b80e69dddb665eb2de36e62859ab2073470e
- git.kernel.org/stable/c/b39f763d720d623218bc1d95ace6855d7b474e81
- git.kernel.org/stable/c/d9e47e29aacb9f8a9d59feb6ab5b128a9bbb40b0
- git.kernel.org/stable/c/f99ac36b5d7c719d08a69fcdecce40f78a874e15
- git.kernel.org/stable/c/f9ef3db77a383d66847fd082c2b437d8ae4d9c63
- git.kernel.org/stable/c/fa6e90bc443bed8dc0d55bc5ea5b27ffdfe37704
- cert-portal.siemens.com/productcert/html/ssa-784472.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.