🛡️ CVE-2025-40350 — kernel

🔴 CVSS 9.8 — Critical ✅ No Known Exploit NVD
9.8
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ

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

net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ

XDP programs can change the layout of an xdp_buff through

bpf_xdp_adjust_tail() and bpf_xdp_adjust_head(). Therefore, the driver

cannot assume the size of the linear data area nor fragments. Fix the

bug in mlx5 by generating skb according to xdp_buff after XDP programs

run.

Currently, when handling multi-buf XDP, the mlx5 driver assumes the

layout of an xdp_buff to be unchanged. That is, the linear data area

continues to be empty and fragments remain the same. This may cause

the driver to generate erroneous skb or triggering a kernel

warning. When an XDP program added linear data through

bpf_xdp_adjust_head(), the linear data will be ignored as

mlx5e_build_linear_skb() builds an skb without linear data and then

pull data from fragments to fill the linear data area. When an XDP

program has shrunk the non-linear data through bpf_xdp_adjust_tail(),

the delta passed to __pskb_pull_tail() may exceed the actual nonlinear

data size and trigger the BUG_ON in it.

To fix the issue, first record the original number of fragments. If the

number of fragments changes after the XDP program runs, rewind the end

fragment pointer by the difference and recalculate the truesize. Then,

build the skb with the linear data area matching the xdp_buff. Finally,

only pull data in if there is non-linear data and fill the linear part

up to 256 bytes.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

Affected software

CVE-2025-40350 is recorded against 2 packages.

  • kernel (from 6.13.0 up to 6.17.6)
  • unknown

Timeline and source

Published on 16 December 2025 and last revised on 6 August 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2025-40350 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Critical
CVSS Score 9.8
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2025-12-16
Updated 2026-08-12
Modified 2026-08-06
Fix URL N/A

Affected Packages

Software From version Fixed in
kernel 6.13.0 6.17.6
unknown

Similar Threats

Exploit Protection

Are you running kernel?

CVE-2025-40350 carries CVSS 9.8 Critical rating. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2025-40350 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2025