CVE-2025-40231: vsock: fix lock inversion in vsock_assign_transport()
Noroxi assessment
Priority: Monitor (action score 0/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.20% (FIRST EPSS).
- Fixed version: Linux Linux 09bba278ccde25a14b6e5088a9e65a8717d0cccf, 251caee792a21eb0b781aab91362b422c945e162, 42ed0784d11adebf748711e503af0eb9f1e6d81d.
Low priority for now. Upgrade to Linux Linux 09bba278ccde25a14b6e5088a9e65a8717d0cccf, 251caee792a21eb0b781aab91362b422c945e162, 42ed0784d11adebf748711e503af0eb9f1e6d81d 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: vsock: fix lock inversion in vsock_assign_transport() Syzbot reported a potential lock inversion deadlock between vsock_register_mutex and sk_lock-AF_VSOCK when vsock_linger() is called. The issue was introduced by commit 687aa0c5581b ("vsock: Fix transport_* TOCTOU") which added vsock_register_mutex locking in vsock_assign_transport() around the transport->release() call, that can call vsock_linger(). vsock_assign_transport() can be called with sk_lock held. vsock_linger() calls sk_wait_event() that temporarily releases and re-acquires sk_lock. During this window, if another thread hold vsock_register_mutex while trying to acquire sk_lock, a circular dependency is created. Fix this by releasing vsock_register_mutex before calling transport->release() and vsock_deassign_transport(). This is safe because we don't need to hold vsock_register_mutex while releasing the old transport, and we ensure the new transport won't disappear by obtaining a module reference first via try_module_get().
- Published
- Dec 4, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
—
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
- 7b73bddf54777fb62d4d8c7729d0affe6df04477, 6.16affected
- 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb and later · before ce4f856c64f0bc30e29302a0ce41f4295ca391c5affected · git
- 36a439049b34cca0b3661276049b84a1f76cc21a and later · before 09bba278ccde25a14b6e5088a9e65a8717d0cccfaffected · git
- 9ce53e744f18e73059d3124070e960f3aa9902bf and later · before b44182c116778feaa05da52a426aeb9da1878dcfaffected · git
- 9d24bb6780282b0255b9929abe5e8f98007e2c6e and later · before 42ed0784d11adebf748711e503af0eb9f1e6d81daffected · git
- ae2c712ba39c7007de63cb0c75b51ce1caaf1da5 and later · before 251caee792a21eb0b781aab91362b422c945e162affected · git
- 687aa0c5581b8d4aa87fd92973e4ee576b550cdf and later · before a2a4346eea8b4cb75037dbcb20b98cb454324f80affected · git
- 687aa0c5581b8d4aa87fd92973e4ee576b550cdf and later · before f7c877e7535260cc7a21484c994e8ce7e8cb6780affected · git
- 5.10.240 and later · before 5.10.246affected · semver
- 5.15.189 and later · before 5.15.196affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| 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.17.6-1 | 6.17.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40229Dec 4, 2025 · mm/damon/core: fix potential memory leak by cleaning ops_filter in damon_destroy_scheme0Monitor
- ← EarlierCVE-2025-40230Dec 4, 2025 · mm: prevent poison consumption when splitting THP0Monitor
- Later →CVE-2025-40232Dec 4, 2025 · rv: Fully convert enabled_monitors to use list_head as iterator0Monitor
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 | 09bba278ccde25a14b6e5088a9e65a8717d0cccf | Vendor (CNA) |
| Linux Linux | 251caee792a21eb0b781aab91362b422c945e162 | Vendor (CNA) |
| Linux Linux | 42ed0784d11adebf748711e503af0eb9f1e6d81d | Vendor (CNA) |
| Linux Linux | 5.10.246 | Vendor (CNA) |
| Linux Linux | 5.15.196 | Vendor (CNA) |
| Linux Linux | 6.1.158 | Vendor (CNA) |
| Linux Linux | 6.12.56 | Vendor (CNA) |
| Linux Linux | 6.16 | Vendor (CNA) |
| Linux Linux | 6.6.115 | Vendor (CNA) |
| Linux Linux | a2a4346eea8b4cb75037dbcb20b98cb454324f80 | Vendor (CNA) |
| Linux Linux | b44182c116778feaa05da52a426aeb9da1878dcf | Vendor (CNA) |
| Linux Linux | ce4f856c64f0bc30e29302a0ce41f4295ca391c5 | Vendor (CNA) |
| Linux Linux | f7c877e7535260cc7a21484c994e8ce7e8cb6780 | Vendor (CNA) |
| debian:linux | 6.1.158-1 · Debian:12 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/251caee792a21eb0b781aab91362b422c945e162
- git.kernel.org/stable/c/42ed0784d11adebf748711e503af0eb9f1e6d81d
- git.kernel.org/stable/c/a2a4346eea8b4cb75037dbcb20b98cb454324f80
- git.kernel.org/stable/c/b44182c116778feaa05da52a426aeb9da1878dcf
- git.kernel.org/stable/c/ce4f856c64f0bc30e29302a0ce41f4295ca391c5
- git.kernel.org/stable/c/f7c877e7535260cc7a21484c994e8ce7e8cb6780
Vendor advisories and official records. Exploit/PoC links are deliberately left out.