Linux Kernel up to 7.3-rc4 veth drivers/net/veth.c veth_set_channels xdp_prog memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$5k-$25k2.42

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.3-rc4. It has been classified as very critical. This issue affects the function veth_set_channels of the file drivers/net/veth.c of the component veth. Performing a manipulation of the argument xdp_prog results in memory corruption. This vulnerability is cataloged as CVE-2026-98381. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as very critical, was found in Linux Kernel up to 7.3-rc4. This affects the function veth_set_channels of the file drivers/net/veth.c of the component veth. The manipulation of the argument xdp_prog with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: veth: manage XDP program pointers during channel resize veth_set_channels() tears down XDP resources for removed RX queues without clearing rq->xdp_prog. If the program is then detached or replaced, those queues keep the old pointer after bpf_prog_put(). A later channel increase can re-enable NAPI and run the freed program. BUG: unable to handle page fault for address: ffffc90000256048 Oops: Oops: 0000 [#1] SMP KASAN NOPTI RIP: veth_xdp_rcv_skb (include/linux/filter.h:779 include/net/xdp.h:696 drivers/net/veth.c:820) Call Trace: veth_xdp_rcv (drivers/net/veth.c:941) veth_poll (drivers/net/veth.c:986) __napi_poll (net/core/dev.c:7787) net_rx_action (net/core/dev.c:7850 net/core/dev.c:8007) handle_softirqs (kernel/softirq.c:645) Kernel panic - not syncing: Fatal exception in interrupt

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-98381 since 09/25/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 10/09/2026).

Upgrading to version 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9 or 7.3-rc5 eliminates this vulnerability. Applying the patch 7a8e143109ff2736dc79e41dcd55af7ceab7520a/1a5c5b9c64ba5f39dba55da6e12561ca56eeb758/f0e8dba8c224981e53c792c6b3dbb7604fb2c2c6/3c10a5dd0d38f506f671dbb59e9d0ee4c72076f9/25bb7c36225220d30f404d7e29d2e052bc5f4b99/43f6b647f209591b1e3f726bb16b8dcba6b95908/7104a370714346b667712913dc16abf14bbc97ed is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-95536). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.222/6.1.189/6.6.158/6.12.112/6.18.55/7.2.9/7.3-rc5
Patch: 7a8e143109ff2736dc79e41dcd55af7ceab7520a/1a5c5b9c64ba5f39dba55da6e12561ca56eeb758/f0e8dba8c224981e53c792c6b3dbb7604fb2c2c6/3c10a5dd0d38f506f671dbb59e9d0ee4c72076f9/25bb7c36225220d30f404d7e29d2e052bc5f4b99/43f6b647f209591b1e3f726bb16b8dcba6b95908/7104a370714346b667712913dc16abf14bbc97ed

Timelineinfo

09/25/2026 CVE reserved
10/09/2026 +14 days Advisory disclosed
10/09/2026 +0 days VulDB entry created
10/09/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-98381 (🔒)
GCVE (CVE): GCVE-0-2026-98381
GCVE (VulDB): GCVE-100-415749
EUVD: 🔒

Entryinfo

Created: 10/09/2026 10:02
Updated: 10/09/2026 11:29
Changes: 10/09/2026 10:02 (61), 10/09/2026 11:29 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!