CVE-2025-39951: um: virtio_uml: Fix use-after-free after put_device in probe
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 00e98b5a69034b251bb36dc6e7123d7648e218e4, 14c231959a16ca41bfdcaede72483362a8c645d7, 4f364023ddcfe83f7073b973a9cb98584b7f2a46.
Low priority for now. Upgrade to Linux Linux 00e98b5a69034b251bb36dc6e7123d7648e218e4, 14c231959a16ca41bfdcaede72483362a8c645d7, 4f364023ddcfe83f7073b973a9cb98584b7f2a46 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 4, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.5affected
- 04e5b1fb01834a602acaae2276b67a783a8c6159 and later · before 14c231959a16ca41bfdcaede72483362a8c645d7affected · git
- 04e5b1fb01834a602acaae2276b67a783a8c6159 and later · before 5e94e44c9cb30d7a383d8ac227f24a8c9326b770affected · git
- 04e5b1fb01834a602acaae2276b67a783a8c6159 and later · before aaf900a83508c8cd5cdf765e7749f9076196ec7faffected · git
- 04e5b1fb01834a602acaae2276b67a783a8c6159 and later · before 4f364023ddcfe83f7073b973a9cb98584b7f2a46affected · git
- 04e5b1fb01834a602acaae2276b67a783a8c6159 and later · before 00e98b5a69034b251bb36dc6e7123d7648e218e4affected · git
- 04e5b1fb01834a602acaae2276b67a783a8c6159 and later · before c2ff91255e0157b356cff115d8dc3eeb5162edf2affected · git
- 04e5b1fb01834a602acaae2276b67a783a8c6159 and later · before 7ebf70cf181651fe3f2e44e95e7e5073d594c9c0affected · git
- before 5.5not affected · semver
- 5.10.245 and later · up to and including 5.10.*not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.5 and later · before 5.10.245
- linux linux kernel5.11 and later · before 5.15.194
- linux linux kernel5.16 and later · before 6.1.154
- linux linux kernel6.2 and later · before 6.6.108
- linux linux kernel6.7 and later · before 6.12.49
- linux linux kernel6.13 and later · before 6.16.9
- linux linux kernel6.17
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux-6.1 | before 6.1.158-1~deb11u1 | 6.1.158-1~deb11u1 |
| Debian:12 | linux | before 6.1.158-1 | 6.1.158-1 |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.16.9-1 | 6.16.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-39949Oct 4, 2025 · qed: Don't collect too many protection override GRC elements22Monitor
- ← EarlierCVE-2025-39950Oct 4, 2025 · net/tcp: Fix a NULL pointer dereference when using TCP-AO with TCP_REPAIR22Monitor
- Later →CVE-2025-39952Oct 4, 2025 · wifi: wilc1000: avoid buffer overflow in WID string configuration31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 00e98b5a69034b251bb36dc6e7123d7648e218e4 | Vendor (CNA) |
| Linux Linux | 14c231959a16ca41bfdcaede72483362a8c645d7 | Vendor (CNA) |
| Linux Linux | 4f364023ddcfe83f7073b973a9cb98584b7f2a46 | Vendor (CNA) |
| Linux Linux | 5e94e44c9cb30d7a383d8ac227f24a8c9326b770 | Vendor (CNA) |
| Linux Linux | 7ebf70cf181651fe3f2e44e95e7e5073d594c9c0 | Vendor (CNA) |
| Linux Linux | aaf900a83508c8cd5cdf765e7749f9076196ec7f | Vendor (CNA) |
| Linux Linux | c2ff91255e0157b356cff115d8dc3eeb5162edf2 | Vendor (CNA) |
| debian:linux | 6.1.158-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.158-1~deb11u1 · Debian:11 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/14c231959a16ca41bfdcaede72483362a8c645d7
- git.kernel.org/stable/c/4f364023ddcfe83f7073b973a9cb98584b7f2a46
- git.kernel.org/stable/c/5e94e44c9cb30d7a383d8ac227f24a8c9326b770
- git.kernel.org/stable/c/7ebf70cf181651fe3f2e44e95e7e5073d594c9c0
- git.kernel.org/stable/c/aaf900a83508c8cd5cdf765e7749f9076196ec7f
- git.kernel.org/stable/c/c2ff91255e0157b356cff115d8dc3eeb5162edf2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.