vmci_host: fix a race condition in vmci_host_poll() causing GPF
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.22% (FIRST EPSS).
- Fixed version: Linux Linux 2053e93ac15519ed1f1fe6eba79a33a4963be4a3, 67e35824f861a05b44b19d38e16a83f653bd9d92, 770d30b1355c6c8879973dd054fca9168def182c.
Low priority for now. Upgrade to Linux Linux 2053e93ac15519ed1f1fe6eba79a33a4963be4a3, 67e35824f861a05b44b19d38e16a83f653bd9d92, 770d30b1355c6c8879973dd054fca9168def182c 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: vmci_host: fix a race condition in vmci_host_poll() causing GPF During fuzzing, a general protection fault is observed in vmci_host_poll(). general protection fault, probably for non-canonical address 0xdffffc0000000019: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x00000000000000c8-0x00000000000000cf] RIP: 0010:__lock_acquire+0xf3/0x5e00 kernel/locking/lockdep.c:4926 <- omitting registers -> Call Trace: <TASK> lock_acquire+0x1a4/0x4a0 kernel/locking/lockdep.c:5672 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0xb3/0x100 kernel/locking/spinlock.c:162 add_wait_queue+0x3d/0x260 kernel/sched/wait.c:22 poll_wait include/linux/poll.h:49 [inline] vmci_host_poll+0xf8/0x2b0 drivers/misc/vmw_vmci/vmci_host.c:174 vfs_poll include/linux/poll.h:88 [inline] do_pollfd fs/select.c:873 [inline] do_poll fs/select.c:921 [inline] do_sys_poll+0xc7c/0x1aa0 fs/select.c:1015 __do_sys_ppoll fs/select.c:1121 [inline] __se_sys_ppoll+0x2cc/0x330 fs/select.c:1101 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4e/0xa0 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Example thread interleaving that causes the general protection fault is as follows: CPU1 (vmci_host_poll) CPU2 (vmci_host_do_init_context) ----- ----- // Read uninitialized context context = vmci_host_dev->context; // Initialize context vmci_host_dev->context = vmci_ctx_create(); vmci_host_dev->ct_type = VMCIOBJ_CONTEXT; if (vmci_host_dev->ct_type == VMCIOBJ_CONTEXT) { // Dereferencing the wrong pointer poll_wait(..., &context->host_context); } In this scenario, vmci_host_poll() reads vmci_host_dev->context first, and then reads vmci_host_dev->ct_type to check that vmci_host_dev->context is initialized. However, since these two reads are not atomically executed, there is a chance of a race condition as described above. To fix this race condition, read vmci_host_dev->context after checking the value of vmci_host_dev->ct_type so that vmci_host_poll() always reads an initialized context.
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th 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
- 3.9affected
- 8bf503991f87e32ea42a7bd69b79ba084fddc5d7 and later · before 2053e93ac15519ed1f1fe6eba79a33a4963be4a3affected · git
- 8bf503991f87e32ea42a7bd69b79ba084fddc5d7 and later · before ca0f4ad2b7a36c799213ef0a213eb977a51e03dcaffected · git
- 8bf503991f87e32ea42a7bd69b79ba084fddc5d7 and later · before 85b4aa4eb2e3a0da111fd0a1cdbf00f986ac6b6baffected · git
- 8bf503991f87e32ea42a7bd69b79ba084fddc5d7 and later · before 770d30b1355c6c8879973dd054fca9168def182caffected · git
- 8bf503991f87e32ea42a7bd69b79ba084fddc5d7 and later · before d22b2a35729cb1de311cb650cd67518a24e13fc9affected · git
- 8bf503991f87e32ea42a7bd69b79ba084fddc5d7 and later · before 67e35824f861a05b44b19d38e16a83f653bd9d92affected · git
- 8bf503991f87e32ea42a7bd69b79ba084fddc5d7 and later · before ab64bd32b9fac27ff4737d63711b9db5e5462448affected · git
- 8bf503991f87e32ea42a7bd69b79ba084fddc5d7 and later · before ae13381da5ff0e8e084c0323c3cc0a945e43e9c7affected · git
- before 3.9not affected · 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.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-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-2023-54005Dec 24, 2025 · binder: fix memory leak in binder_init()0Monitor
- ← EarlierCVE-2023-54006Dec 24, 2025 · af_unix: Fix data-race around unix_tot_inflight.0Monitor
- Later →CVE-2023-54008Dec 24, 2025 · virtio_vdpa: build affinity masks conditionally0Monitor
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 | 2053e93ac15519ed1f1fe6eba79a33a4963be4a3 | Vendor (CNA) |
| Linux Linux | 67e35824f861a05b44b19d38e16a83f653bd9d92 | Vendor (CNA) |
| Linux Linux | 770d30b1355c6c8879973dd054fca9168def182c | Vendor (CNA) |
| Linux Linux | 85b4aa4eb2e3a0da111fd0a1cdbf00f986ac6b6b | Vendor (CNA) |
| Linux Linux | ab64bd32b9fac27ff4737d63711b9db5e5462448 | Vendor (CNA) |
| Linux Linux | ae13381da5ff0e8e084c0323c3cc0a945e43e9c7 | Vendor (CNA) |
| Linux Linux | ca0f4ad2b7a36c799213ef0a213eb977a51e03dc | Vendor (CNA) |
| Linux Linux | d22b2a35729cb1de311cb650cd67518a24e13fc9 | Vendor (CNA) |
| debian:linux | 6.1.37-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 (7 more)Show less
- git.kernel.org/stable/c/67e35824f861a05b44b19d38e16a83f653bd9d92
- git.kernel.org/stable/c/770d30b1355c6c8879973dd054fca9168def182c
- git.kernel.org/stable/c/85b4aa4eb2e3a0da111fd0a1cdbf00f986ac6b6b
- git.kernel.org/stable/c/ab64bd32b9fac27ff4737d63711b9db5e5462448
- git.kernel.org/stable/c/ae13381da5ff0e8e084c0323c3cc0a945e43e9c7
- git.kernel.org/stable/c/ca0f4ad2b7a36c799213ef0a213eb977a51e03dc
- git.kernel.org/stable/c/d22b2a35729cb1de311cb650cd67518a24e13fc9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.