Is there a patch available for EUVD-2026-103790?

Yes, a patch is available for EUVD-2026-103790. Update the affected software to the latest version immediately.

Linux EUVD-2026-103790

| CVE-2026-98850

2026-10-18 Linux

GHSA-prpm-w567-3rvc

View

Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives.

Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

In the Linux kernel, the following vulnerability has been resolved:

net/packet: prevent TX_RING byte count overflow

tpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds each valid packet length to the signed int len_sum. Userspace can recycle completed frames concurrently, so a single blocking send call is not bounded by the ring size.

After enough successful transmissions len_sum wraps into the negative range. In particular, 65536 65535-byte frames followed by a 65007-byte frame produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats that as an impossible return and triggers a BUG. On systems configured to panic on oops, a CAP_NET_RAW holder can panic the host kernel.

Stop before the next frame would make the byte count exceed INT_MAX. The positive short count leaves that frame pending for a later send call.

A two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build of Linux 7.3-rc4. With this change, the same reproducer returned the expected positive short count without an oops.

Affected VersionsENISA

Linux 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <be12b221c0301111eeb023be04add3c6ad7c21fe

Linux patch: 0

Linux 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <9fd63d284e251332f4874ef9023cde472f315f86

Linux patch: 6.12.113

Linux 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <2cf81fc9505b148b1b70068303ea6ea4b1212403

Linux patch: 7.2.10

Linux patch: 7.3-rc6

Linux 2.6.31

Linux 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <69ca64bbb528898916f309552053c32a04a36ebc

Linux patch: 6.18.56

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Lifecycle Timeline

Patch available

Oct 18, 2026 - 17:19 EUVD

CVE Published

Oct 18, 2026 - 15:50 cve.org

UNKNOWN (no severity yet)

Threat Intelligence Overview

Data Quality

1 sources

Confidence: Low

EUVD

CVE.org

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity Not scored yet

CISA KEV No

Public POC No

EPSS N/A

Patch available Yes

Active threat No

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives.

Attack Technique

Buffer Overflow HIGH

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.