cveboard RSS feed

CVE-2025-40350

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2025
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
f52ac7028bec22e925c8fece4f21641eb13b4d6faffectedgit8b051d7f530e8a5237da242fbeafef02fec6b813UnavailableNone listed
f52ac7028bec22e925c8fece4f21641eb13b4d6faffectedgitcb9edd583e23979ee546981be963ad5f217e8b18UnavailableNone listed
f52ac7028bec22e925c8fece4f21641eb13b4d6faffectedgitf2557d7fa38e9475b38588f5c124476091480f53UnavailableNone listed
f52ac7028bec22e925c8fece4f21641eb13b4d6faffectedgit87bcef158ac1faca1bd7e0104588e8e2956d10beUnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
6.4affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver6.4UnavailableNone listed
6.6.115unaffectedsemverUnavailable6.6.*None listed
6.12.56unaffectedsemverUnavailable6.12.*None listed
6.17.6unaffectedsemverUnavailable6.17.*None listed
6.18unaffectedoriginal_commit_for_fixUnavailable*None listed