Description
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.
Published: 2026-10-18
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Kernel Panic via Integer Overflow
Action: Apply Patch
AI Analysis

Impact

The vulnerability stems from an unchecked accumulation of packet lengths in the TX ring. Each validated transmit request adds its length to a signed integer counter. When the total exceeds the maximum positive value for that type, the counter overflows into the negative range, producing a result that triggers a BUG in the kernel. For a CAP_NET_RAW holder, this BUG causes the kernel to panic, halting the entire system. The flaw does not directly expose information or provide remote code execution but results in denial of service at the operating system level.

Affected Systems

All Linux kernel versions that implement the tpacket TX ring logic before the patch are affected, including the arm64 build of Linux 7.3-rc4 where the issue was originally reproduced. The problem exists in any kernel configuration that creates and uses TPACKET_V2 transmission rings for packet capture or sending.

Risk and Exploitability

The risk is moderate (CVSS 5.5) because an attacker with CAP_NET_RAW privileges can trigger a kernel crash by sending numerous large packets, causing the system to become unavailable. The exploit requires local or privileged access; remote exploitation is not indicated by the available data. The EPSS score is < 1% and the vulnerability is not currently listed in the CISA KEV catalog, but the potential for a catastrophic denial of service warrants immediate attention.

Generated by OpenCVE AI on October 24, 2026 at 13:52 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the kernel patch that limits the TX_RING byte count before it exceeds INT_MAX, as referenced in the provided commits.
  • Upgrade to a Linux kernel release that includes this fix if patching is not feasible.
  • Restrict CAP_NET_RAW capability to trusted processes only to reduce the likelihood that a malicious user can trigger the overflow.

Generated by OpenCVE AI on October 24, 2026 at 13:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4850-1 linux-6.12 security update
History

Fri, 30 Oct 2026 13:00:00 +0000


Sat, 24 Oct 2026 12:30:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Wed, 21 Oct 2026 13:15:00 +0000


Sun, 18 Oct 2026 21:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-190

Sun, 18 Oct 2026 16:00:00 +0000

Type Values Removed Values Added
Description 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.
Title net/packet: prevent TX_RING byte count overflow
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-30T12:40:11.960Z

Reserved: 2026-09-25T10:25:14.376Z

Link: CVE-2026-98850

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-18T16:17:39.390

Modified: 2026-10-30T13:21:30.597

Link: CVE-2026-98850

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-18T00:00:00Z

Links: CVE-2026-98850 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-24T14:00:17Z

Weaknesses
  • CWE-190

    Integer Overflow or Wraparound