CVE-2025-39951 json
um: virtio_uml: Fix use-after-free after put_device in probe
published last yr. modified 21d ago also EUVD-2025-32394
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
um: virtio_uml: Fix use-after-free after put_device in probe
When register_virtio_device() fails in virtio_uml_probe(), the code sets vu_dev->registered = 1 even though the device was not successfully registered. This can lead to use-after-free or other issues.
Patch / fix
- Linux Linux 5.10.245, 5.15.194, 6.1.154, 6.6.108, 6.12.49, 6.16.9, 6.17
- linux Debian 12 6.1.158-1
- linux Debian 13 6.12.57-1
- linux Debian 14 6.16.9-1
debian advisories DEBIAN-CVE-2025-39951
- linux Ubuntu 22.04 LTS 5.15.0-170.180
- linux Ubuntu 24.04 LTS 6.8.0-106.106
- linux-aws Ubuntu 22.04 LTS 5.15.0-1100.107
- linux-aws Ubuntu 24.04 LTS 6.8.0-1050.53
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1100.109
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1052.55
- linux-gke Ubuntu 22.04 LTS 5.15.0-1096.102
- linux-gke Ubuntu 24.04 LTS 6.8.0-1048.53
ubuntu advisories UBUNTU-CVE-2025-39951
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/14c231959a16ca41bfdcaede72483362a8c645d7 commit
- git.kernel.org/stable/c/5e94e44c9cb30d7a383d8ac227f24a8c9326b770 commit
- git.kernel.org/stable/c/aaf900a83508c8cd5cdf765e7749f9076196ec7f commit
- git.kernel.org/stable/c/4f364023ddcfe83f7073b973a9cb98584b7f2a46 commit
- git.kernel.org/stable/c/00e98b5a69034b251bb36dc6e7123d7648e218e4 commit
- git.kernel.org/stable/c/c2ff91255e0157b356cff115d8dc3eeb5162edf2 commit
- git.kernel.org/stable/c/7ebf70cf181651fe3f2e44e95e7e5073d594c9c0 commit
Is CVE-2025-39951 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-39951 updated
kernel: um: virtio_uml: Fix use-after-free after put_device in probe
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
git.kernel.org
/stable/c/14c231959a16ca41bfdcaede72483362a8c645d7
patch
-
git.kernel.org
/stable/c/5e94e44c9cb30d7a383d8ac227f24a8c9326b770
patch
-
git.kernel.org
/stable/c/aaf900a83508c8cd5cdf765e7749f9076196ec7f
patch
-
git.kernel.org
/stable/c/4f364023ddcfe83f7073b973a9cb98584b7f2a46
patch
-
git.kernel.org
/stable/c/00e98b5a69034b251bb36dc6e7123d7648e218e4
patch
-
git.kernel.org
/stable/c/c2ff91255e0157b356cff115d8dc3eeb5162edf2
patch
-
git.kernel.org
/stable/c/7ebf70cf181651fe3f2e44e95e7e5073d594c9c0
patch
Sources
- CVE List CVE-2025-39951
- NVD CVE-2025-39951
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.