CVE-2025-40104

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-10-30. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

ixgbevf: fix mailbox API compatibility by negotiating supported features

There was backward compatibility in the terms of mailbox API. Various drivers from various OSes supporting 10G adapters from Intel portfolio could easily negotiate mailbox API.

This convention has been broken since introducing API 1.4. Commit 0062e7cc955e ("ixgbevf: add VF IPsec offload code") added support for IPSec which is specific only for the kernel ixgbe driver. None of the rest of the Intel 10G PF/VF drivers supports it. And actually lack of support was not included in the IPSec implementation - there were no such code paths. No possibility to negotiate support for the feature was introduced along with introduction of the feature itself.

Commit 339f28964147 ("ixgbevf: Add support for new mailbox communication between PF and VF") increasing API version to 1.5 did the same - it introduced code supported specifically by the PF ESX driver. It altered API version for the VF driver in the same time not touching the version defined for the PF ixgbe driver. It led to additional discrepancies, as the code provided within API 1.6 cannot be supported for Linux ixgbe driver as it causes crashes.

The issue was noticed some time ago and mitigated by Jake within the commit d0725312adf5 ("ixgbevf: stop attempting IPSEC offload on Mailbox API 1.5"). As a result we have regression for IPsec support and after increasing API to version 1.6 ixgbevf driver stopped to support ESX MBX.

To fix this mess add new mailbox op asking PF driver about supported features. Basing on a response determine whether to set support for IPSec and ESX-specific enhanced mailbox.

New mailbox op, for compatibility purposes, must be added within new API revision, as API version of OOT PF & VF drivers is already increased to 1.6 and doesn't incorporate features negotiate op.

Features negotiation mechanism gives possibility to be extended with new features when needed in the future.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

October 30, 2025

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Jul 31, 2026
No patch confirmed yet.
generic

ixgbevf: fix mailbox API compatibility by negotiating supported features - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bf580112ed61736c2645a893413a04732505d4b1
generic

ixgbevf: fix mailbox API compatibility by negotiating supported features - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a7075f501bd33c93570af759b6f4302ef0175168
generic

ixgbevf: fix mailbox API compatibility by negotiating supported features - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a376e29b1b196dc90b50df7e5e3947e3026300c4
generic

ixgbevf: fix mailbox API compatibility by negotiating supported features - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/871ac1cd4ce4804defcb428cbb003fd84c415ff4
generic

ixgbevf: fix mailbox API compatibility by negotiating supported features - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e0aab9ddaf1428602c78f12064cd1e6ffcc4d18

Vendor Advisories for CVE-2025-40104(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(16)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-07-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-07-30ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1007.7) @ questing2026-07-30ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1007.7) @ questing2026-07-30ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1008.8) @ questing2026-07-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-07-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-07-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-07-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-14.14) @ questing2026-07-30ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1011.11) @ noble2026-07-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-07-30ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1049.52~22.04.1) @ jammy2026-07-30ubuntu
linuxKernel @ 6.1.158—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(16)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 14× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 141 total refreshes for this CVE.

  1. 2026-08-05 12:53 UTCEG score recompute
  2. 2026-08-05 12:53 UTCVendor advisory
  3. 2026-08-05 12:52 UTCGHSA enrichment
  4. 2026-08-04 15:09 UTCEPSS rescore
  5. 2026-08-04 10:37 UTCEPSS rescore
  6. 2026-08-03 10:35 UTCEPSS rescore
  7. 2026-08-02 02:26 UTCEPSS rescore
  8. 2026-08-01 04:15 UTCEPSS rescore
  9. 2026-07-30 16:27 UTCEPSS rescore
  10. 2026-07-30 06:29 UTCEG score recompute▲ 7.80
  11. 2026-07-30 06:29 UTCVendor advisory
  12. 2026-07-30 06:29 UTCGHSA enrichment
  13. 2026-07-30 06:18 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-07-30 01:29 UTCEPSS rescore
  15. 2026-07-28 15:35 UTCEPSS rescore
  16. 2026-07-27 08:39 UTCOSV refresh
  17. 2026-07-26 14:54 UTCEPSS rescore
  18. 2026-07-24 14:17 UTCEPSS rescore
  19. 2026-07-23 02:55 UTCEG score recompute
  20. 2026-07-22 14:07 UTCEPSS rescore
  21. 2026-07-22 14:07 UTCEPSS rescore
  22. 2026-07-21 15:24 UTCEPSS rescore
  23. 2026-07-20 17:07 UTCEPSS rescore
  24. 2026-07-19 14:30 UTCEPSS rescore
  25. 2026-07-19 14:30 UTCEPSS rescore
Show 75 more
  1. 2026-07-19 02:28 UTCEPSS rescore
  2. 2026-07-19 02:28 UTCEPSS rescore
  3. 2026-07-18 10:04 UTCEPSS rescore
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-16 17:02 UTCEPSS rescore
  6. 2026-07-15 16:57 UTCEPSS rescore
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-15 01:59 UTCEPSS rescore
  9. 2026-07-15 01:59 UTCEPSS rescore
  10. 2026-07-13 22:29 UTCEPSS rescore
  11. 2026-07-13 22:29 UTCEPSS rescore
  12. 2026-07-13 06:12 UTCEPSS rescore
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-10 02:53 UTCOSV refresh
  17. 2026-07-09 19:09 UTCEPSS rescore
  18. 2026-07-09 19:09 UTCEPSS rescore
  19. 2026-07-07 13:45 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-05 02:30 UTCEPSS rescore
  24. 2026-07-04 06:30 UTCEPSS rescore
  25. 2026-07-01 15:06 UTCEPSS rescore
  26. 2026-07-01 15:06 UTCEPSS rescore
  27. 2026-06-30 23:22 UTCEPSS rescore
  28. 2026-06-30 23:22 UTCEPSS rescore
  29. 2026-06-29 14:06 UTCEPSS rescore
  30. 2026-06-29 14:06 UTCEPSS rescore
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 14:07 UTCEPSS rescore
  33. 2026-06-28 04:55 UTCEPSS rescore
  34. 2026-06-28 04:55 UTCEPSS rescore
  35. 2026-06-27 03:08 UTCEPSS rescore
  36. 2026-06-27 03:08 UTCEPSS rescore
  37. 2026-06-25 13:49 UTCEPSS rescore
  38. 2026-06-25 13:49 UTCEPSS rescore
  39. 2026-06-24 14:04 UTCEPSS rescore
  40. 2026-06-24 14:04 UTCEPSS rescore
  41. 2026-06-23 21:32 UTCEPSS rescore
  42. 2026-06-23 21:32 UTCEPSS rescore
  43. 2026-06-22 14:25 UTCEPSS rescore
  44. 2026-06-22 14:25 UTCEPSS rescore
  45. 2026-06-21 14:56 UTCEPSS rescore
  46. 2026-06-21 14:56 UTCEPSS rescore
  47. 2026-06-21 13:31 UTCOSV refresh
  48. 2026-06-21 01:59 UTCEPSS rescore
  49. 2026-06-21 01:59 UTCEPSS rescore
  50. 2026-06-19 19:25 UTCEPSS rescore
  51. 2026-06-19 19:25 UTCEPSS rescore
  52. 2026-06-18 17:52 UTCEPSS rescore
  53. 2026-06-18 17:52 UTCEPSS rescore
  54. 2026-06-17 17:52 UTCEPSS rescore
  55. 2026-06-16 17:52 UTCEPSS rescore
  56. 2026-06-16 17:52 UTCEPSS rescore
  57. 2026-06-14 23:17 UTCEPSS rescore
  58. 2026-06-13 23:00 UTCEPSS rescore
  59. 2026-06-12 23:11 UTCEPSS rescore
  60. 2026-06-11 14:00 UTCEPSS rescore
  61. 2026-06-10 22:18 UTCEPSS rescore
  62. 2026-06-10 13:22 UTCEPSS rescore
  63. 2026-06-08 14:16 UTCEPSS rescore
  64. 2026-06-08 14:16 UTCEPSS rescore
  65. 2026-06-07 15:24 UTCEPSS rescore
  66. 2026-06-06 13:47 UTCEPSS rescore
  67. 2026-06-06 13:47 UTCEPSS rescore
  68. 2026-06-05 22:46 UTCEPSS rescore
  69. 2026-06-05 22:46 UTCEPSS rescore
  70. 2026-06-05 06:10 UTCEPSS rescore
  71. 2026-06-05 06:10 UTCEPSS rescore
  72. 2026-06-04 13:12 UTCEPSS rescore
  73. 2026-06-04 13:12 UTCEPSS rescore
  74. 2026-06-02 20:12 UTCEPSS rescore
  75. 2026-06-02 08:09 UTCOSV refresh

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2025-40104?
CVE-2025-40104 is a high vulnerability published on October 30, 2025. In the Linux kernel, the following vulnerability has been resolved: ixgbevf: fix mailbox API compatibility by negotiating supported features There was backward compatibility in the terms of mailbox API. Various drivers from various OSes supporting 10G adapters from Intel portfolio could easily…
When was CVE-2025-40104 disclosed?
CVE-2025-40104 was first published in the National Vulnerability Database on October 30, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-40104 actively exploited?
CVE-2025-40104 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.9% of all scored CVEs.
What is the CVSS score of CVE-2025-40104?
CVE-2025-40104 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-40104?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-40104, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-40104

Explore →

Is Your Infrastructure Affected by CVE-2025-40104?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs