Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 8 months later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-40350, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.59% · top 51% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected f52ac7028bec22e925c8fece4f21641eb13b4d6f – < 8b051d7f530e8a5237da242fbeafef02fec6b813
    • affected f52ac7028bec22e925c8fece4f21641eb13b4d6f – < cb9edd583e23979ee546981be963ad5f217e8b18
    • affected f52ac7028bec22e925c8fece4f21641eb13b4d6f – < f2557d7fa38e9475b38588f5c124476091480f53
    • affected f52ac7028bec22e925c8fece4f21641eb13b4d6f – < 87bcef158ac1faca1bd7e0104588e8e2956d10be
  • Linux · Linux

    • affected 6.4
    • unaffected < 6.4
    • unaffected 6.6.115 – ≤ 6.6.*
    • unaffected 6.12.56 – ≤ 6.12.*
    • unaffected 6.17.6 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-40350 badge
[![CVE-2025-40350](https://cveledger.app/badge/CVE-2025-40350.svg)](https://cveledger.app/cve/CVE-2025-40350)

Record last updated .