Unspecified impact via unchecked VF ring lengths
Published Oct 15, 2025 · Updated Oct 15, 2025
Improper input validation in the Linux i40e PF driver allows local users to cause unspecified impact via crafted VF queue messages. The queue-configuration path copies each VF-supplied ring_len directly into the hardware memory context without checking the 8K-minus-32 limit or Tx/Rx alignment. Reaching the path outside standard iavf checks requires CAP_SYS_MODULE or CAP_SYS_ADMIN in the initial user namespace; the upstream notice does not specify the resulting failure mode.
Summary
What happened
Improper input validation in the Linux i40e PF driver allows local users to cause unspecified impact via crafted VF queue messages. The queue-configuration path copies each VF-supplied ring_len directly into the hardware memory context without checking the 8K-minus-32 limit or Tx/Rx alignment. Reaching the path outside standard iavf checks requires CAP_SYS_MODULE or CAP_SYS_ADMIN in the initial user namespace; the upstream notice does not specify the resulting failure mode.
The record
- CVE
- CVE-2025-39973
- Published
- Oct 15, 2025
- Updated
- Oct 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 15, 2025CVE publishedPublication date reported by the CVE source.
- Oct 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.12
- Affected versionversion=5c3c48ac6bf56367c4e89f6453cd2d61e50375bd <0543d40d6513cdf1c7882811086e59a6455dfe97
- Affected versionversion=5c3c48ac6bf56367c4e89f6453cd2d61e50375bd <05fe81fb9db20464fa532a3835dc8300d68a2f84
- Affected versionversion=5c3c48ac6bf56367c4e89f6453cd2d61e50375bd <45a7527cd7da4cdcf3b06b5c0cb1cae30b5a5985
- Affected versionversion=5c3c48ac6bf56367c4e89f6453cd2d61e50375bd <55d225670def06b01af2e7a5e0446fbe946289e8
- Affected versionversion=5c3c48ac6bf56367c4e89f6453cd2d61e50375bd <7d749e38dd2b7e8a80da2ca30c93e09de95bfcf9
- Affected versionversion=5c3c48ac6bf56367c4e89f6453cd2d61e50375bd <afec12adab55d10708179a64d95d650741e60fe0
- Affected versionversion=5c3c48ac6bf56367c4e89f6453cd2d61e50375bd <c0c83f4cd074b75cecef107bfc349be7d516c9c4
- Affected versionversion=5c3c48ac6bf56367c4e89f6453cd2d61e50375bd <d3b0d3f8d11fa957171fbb186e53998361a88d4e
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo