Skip to main content

Linux EUVDEUVD-2026-15367

| CVE-2026-23377 MEDIUM
2026-03-25 Linux GHSA-r46f-q3f8-wrrg
5.5
CVSS 3.1 · NVD
View

Vulnerability Assessment

Impact

This vulnerability presents a moderate to high real-world risk despite the absence of a CVSS score and EPSS value. The vulnerability is not listed in the Known Exploited Vulnerabilities (KEV) catalog, indicating no active in-the-wild exploitation has been confirmed. However, proof-of-concept capability exists through the XSK_UMEM__MAX_FRAME_SIZE test case provided in the description, demonstrating reliable reproducibility. The attack vector requires local access and the ability to load and execute XDP/eBPF programs, which is typically restricted to root or CAP_SYS_RESOURCE/CAP_SYS_ADMIN capable users on most systems. This significantly reduces the attack surface compared to remote vulnerabilities. The impact is a denial of service through kernel panic rather than information disclosure or privilege escalation. Systems running Linux with the ice driver (Intel Ethernet devices) and exposed XDP program loading capabilities are at risk, particularly in cloud environments, containers, or systems where unprivileged XDP is enabled. Patch availability through stable kernel commits (b0f05100e8795aadd1c0606bae9caefbda070d63 and e142dc4ef0f451b7ef99d09aaa84e9389af629d7) indicates this is a known, resolved issue, reducing ongoing risk for patched systems.

Exploit ScenarioDerived

An attacker with local access and XDP program loading capabilities (root or equivalent capabilities) crafts a custom XDP program that calls bpf_xdp_frags_increase_tail() with large offset values (e.g., XSK_UMEM__MAX_FRAME_SIZE * 100) while processing packets of specific sizes (e.g., 6912 bytes). The vulnerable ice driver's incorrect frag_size calculation causes the tailroom computation to become negative, triggering a kernel panic assertion failure or buffer overflow condition in the XDP frame processing code. This results in immediate denial of service affecting all network traffic processed through that driver instance. While a formal proof-of-concept exists via the xskxceiver test suite referenced in the description, real-world exploitation requires the attacker to first obtain XDP program loading privileges, making this primarily a risk vector in multi-tenant cloud environments, container platforms with permissive capabilities, or systems where unprivileged XDP is explicitly enabled.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Mar 25, 2026

A memory buffer management vulnerability exists in the Linux kernel's ice network driver XDP (eXpress Data Path) implementation, specifically in how it calculates fragment buffer sizes for receive queues. The vulnerability affects Linux kernel versions with the vulnerable ice driver code path and can be triggered through XDP operations that attempt to grow multi-buffer packet tails, potentially causing kernel panics or denial of service. An attacker with the ability to load and execute XDP programs can exploit this by crafting specific packet sizes and offset values to trigger the panic condition, as demonstrated by the XSK_UMEM__MAX_FRAME_SIZE test case, though real-world exploitation requires local access to load XDP programs.

RemediationAI

Apply the Linux kernel patches from the stable kernel repository by upgrading to a kernel version that includes commits b0f05100e8795aadd1c0606bae9caefbda070d63 and e142dc4ef0f451b7ef99d09aaa84e9389af629d7. Most Linux distributions will provide these patches through regular security updates to their kernel packages; users should update to the latest stable kernel version available from their distribution. Until patching is possible, restrict XDP program loading capabilities to trusted administrators only by enforcing strict AppArmor or SELinux policies that limit CAP_SYS_RESOURCE and CAP_SYS_ADMIN capabilities. Additionally, disable zero-copy XDP mode if not required, revert to standard packet processing mode, or avoid using XDP_ADJUST_TAIL_GROW_MULTI_BUFF operations until the kernel is patched. Monitor kernel logs for BUG messages related to XDP tail operations as an early warning sign. See upstream kernel patches at https://git.kernel.org/stable/c/b0f05100e8795aadd1c0606bae9caefbda070d63 and https://git.kernel.org/stable/c/e142dc4ef0f451b7ef99d09aaa84e9389af629d7.

Affected VersionsENISA

Linux patch: 0
Linux 6.3
Linux 2fba7dc5157b6f85dbf1b8e26e63a724db1f3d79 <b0f05100e8795aadd1c0606bae9caefbda070d63
Linux 2fba7dc5157b6f85dbf1b8e26e63a724db1f3d79 <e142dc4ef0f451b7ef99d09aaa84e9389af629d7
Linux patch: 6.19.7
Linux patch: 7.0-rc3

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.

Technical ContextAI · show details

The vulnerability exists in the Intel ice Ethernet driver's XDP receive queue (RxQ) configuration within the Linux kernel (affected CPE: cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*). The root cause is a semantic mismatch in the frag_size field used by XDP operations: the ice driver was setting this field to the DMA write length rather than the actual buffer size (xdp.frame_sz). The bpf_xdp_frags_increase_tail() function expects frag_size to represent the entire buffer size to correctly calculate tailroom for multi-buffer XDP packets. When the XDP_ADJUST_TAIL_GROW_MULTI_BUFF operation attempts to grow packet tails, it uses this incorrect frag_size value, resulting in negative tailroom calculations. This is fundamentally a logic error in buffer accounting rather than a memory corruption vulnerability, though it manifests as a denial of service through kernel panic. The fix involves replacing DMA write length with the actual fill queue buffer truesize in both standard and zero-copy (ZC) modes.

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

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SUSE MEDIUM
Red Hat 5.5 MEDIUM

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

3
CVSS changed
Apr 24, 2026 - 16:37 NVD
5.5 (MEDIUM)
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
CVE Published
Mar 25, 2026 - 10:27 nvd
N/A

DescriptionNVD

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

ice: change XDP RxQ frag_size from DMA write length to xdp.frame_sz

The only user of frag_size field in XDP RxQ info is bpf_xdp_frags_increase_tail(). It clearly expects whole buff size instead of DMA write size. Different assumptions in ice driver configuration lead to negative tailroom.

This allows to trigger kernel panic, when using XDP_ADJUST_TAIL_GROW_MULTI_BUFF xskxceiver test and changing packet size to 6912 and the requested offset to a huge value, e.g. XSK_UMEM__MAX_FRAME_SIZE * 100.

Due to other quirks of the ZC configuration in ice, panic is not observed in ZC mode, but tailroom growing still fails when it should not.

Use fill queue buffer truesize instead of DMA write size in XDP RxQ info. Fix ZC mode too by using the new helper.

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Data Quality
6 sources
Confidence: High

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
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.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Related Vulnerabilities in ice Driver Memory and XDP Issues

View all 2

Vendor StatusVendor

Debian

linux
Release Status Fixed Version Urgency
bullseye not-affected - -
bullseye (security) fixed 5.10.251-1 -
bookworm not-affected - -
bookworm (security) fixed 6.1.164-1 -
trixie vulnerable 6.12.73-1 -
trixie (security) vulnerable 6.12.74-2 -
forky, sid fixed 6.19.8-1 -
(unstable) fixed 6.19.8-1 -

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy