CVE-2025-68213
Last modified
CVE-2025-68213 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: idpf: fix possible vport_config NULL pointer deref in remove Attempting to remove the driver will cause a crash in cases where the vport failed to initialize. Following trace is from an instance where the driver failed during an attempt to create a VF: [ 1661.543624] idpf 0000:84:00.7: Device HW Reset initiated [ 1722.923726] idpf 0000:84:00.7: Transaction timed-out (op:1 cookie:2900 vc_op:1 salt:29 timeout:60000ms) [ 1723.353263] BUG: kernel NULL pointer dereference, address: 0000000000000028 ... [ 1723.358472] RIP: 0010:idpf_remove+0x11c/0x200 [idpf] ... [ 1723.364973] Call Trace: [ 1723.365475] <TASK> [ 1723.365972] pci_device_remove+0x42/0xb0 [ 1723.366481] device_release_driver_internal+0x1a9/0x210 [ 1723.366987] pci_stop_bus_device+0x6d/0x90 [ 1723.367488] pci_stop_and_remove_bus_device+0x12/0x20 [ 1723.367971] pci_iov_remove_virtfn+0xbd/0x120 [ 1723.368309] sriov_disable+0x34/0xe0 [ 1723.368643] idpf_sriov_configure+0x58/0x140 [idpf] [ 1723.368982] sriov_numvfs_store+0xda/0x1c0 Avoid the NULL pointer dereference by adding NULL pointer check for vport_config[i], before freeing user_config.q_coalesce.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: idpf: fix possible vport_config NULL pointer deref in remove Attempting to remove the driver will cause a crash in cases where the vport failed to initialize. Following trace is from an instance where the driver failed during an attempt to create a VF: [ 1661.543624] idpf 0000:84:00.7: Device HW Reset initiated [ 1722.923726] idpf 0000:84:00.7: Transaction timed-out (op:1 cookie:2900 vc_op:1 salt:29 timeout:60000ms) [ 1723.353263] BUG: kernel NULL pointer dereference, address: 0000000000000028 ... [ 1723.358472] RIP: 0010:idpf_remove+0x11c/0x200 [idpf] ... [ 1723.364973] Call Trace: [ 1723.365475] <TASK> [ 1723.365972] pci_device_remove+0x42/0xb0 [ 1723.366481] device_release_driver_internal+0x1a9/0x210 [ 1723.366987] pci_stop_bus_device+0x6d/0x90 [ 1723.367488] pci_stop_and_remove_bus_device+0x12/0x20 [ 1723.367971] pci_iov_remove_virtfn+0xbd/0x120 [ 1723.368309] sriov_disable+0x34/0xe0 [ 1723.368643] idpf_sriov_configure+0x58/0x140 [idpf] [ 1723.368982] sriov_numvfs_store+0xda/0x1c0 Avoid the NULL pointer dereference by adding NULL pointer check for vport_config[i], before freeing user_config.q_coalesce.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= bd80fbf3ed250ca98923780dab5e634db5d2f828, < a0e1c9bc1c9fe735978150ad075616a728073bc7; >= e1e3fec3e34b4934a9d2c98e4ee00a4d87b19179, < d5be8663cff0ba7b94da34ebd499ce1123b4c334; >= e1e3fec3e34b4934a9d2c98e4ee00a4d87b19179, < 118082368c2b6ddefe6cb607efc312285148f044; 5e87b3145578a169839e456fa0aba86e123d2d8e; ba11b0f3e9a97661f6caeee3dfc633af8ecee5a5; >= 6.12.43, < 6.12.60; >= 6.15.11, < 6.16; >= 6.16.2, < 6.17 |
| Linux | Linux | 6.17 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-68213?
How severe is CVE-2025-68213?
How do I fix CVE-2025-68213?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-68208In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-68209In the Linux kernel, the following vulnerability has been re…
- CVE-2025-6821A vulnerability was found in code-projects Inventory Managem…9.8
- CVE-2025-68210In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68211In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-68212In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-68214In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-68215In the Linux kernel, the following vulnerability has been re…7
- CVE-2025-68216In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68217In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68218In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2025-68219In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2025-68213?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
