CVE-2025-38569: Linux kernel · benet: fix BUG when creating VFs
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1097.104~20.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.15.0-1097.104~20.04.1, 5.15.0-1102.111~20.04.1, 5.15.0-1097.106~20.04.1 +59
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7764-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7765-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7779-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7764-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7880-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7909-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7909-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7909-3 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-aws-6.14pkg:deb/ubuntu/linux-aws-6.14?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: benet: fix BUG when creating VFs benet crashes as soon as SRIOV VFs are created: kernel BUG at mm/vmalloc.c:3457! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 4 UID: 0 PID: 7408 Comm: test.sh Kdump: loaded Not tainted 6.16.0+ #1 PREEMPT(voluntary) [...] RIP: 0010:vunmap+0x5f/0x70 [...] Call Trace: <TASK> __iommu_dma_free+0xe8/0x1c0 be_cmd_set_mac_list+0x3fe/0x640 [be2net] be_cmd_set_mac+0xaf/0x110 [be2net] be_vf_eth_addr_config+0x19f/0x330 [be2net] be_vf_setup+0x4f7/0x990 [be2net] be_pci_sriov_configure+0x3a1/0x470 [be2net] sriov_numvfs_store+0x20b/0x380 kernfs_fop_write_iter+0x354/0x530 vfs_write+0x9b9/0xf60 ksys_write+0xf3/0x1d0 do_syscall_64+0x8c/0x3d0 be_cmd_set_mac_list() calls dma_free_coherent() under a spin_lock_bh. Fix it by freeing only after the lock has been released.
References
- ubuntu.com/security/CVE-2025-38569 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-38569 (opens in a new tab)
- git.kernel.org/linus/5a40f8af2ba1b9bdf46e2db10e8c9710538fbc63 (opens in a new tab)
- git.kernel.org/stable/c/0ddfe8b127ef1149fddccb79db6e6eaba7738e7d (opens in a new tab)
- git.kernel.org/stable/c/46d44a23a3723a89deeb65b13cddb17f8d9f2700 (opens in a new tab)
- git.kernel.org/stable/c/5a40f8af2ba1b9bdf46e2db10e8c9710538fbc63 (opens in a new tab)
- git.kernel.org/stable/c/c377ba2be9430d165a98e4b782902ed630bc7546 (opens in a new tab)
- git.kernel.org/stable/c/d5dc09ee5d74277bc47193fe28ce8703e229331b (opens in a new tab)
- git.kernel.org/stable/c/f4e4e0c4bc4d799d6fa39055acdbc3af066cd13e (opens in a new tab)
- ubuntu.com/security/notices/USN-7764-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7765-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7779-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7764-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7880-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7909-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7909-2 (opens in a new tab)