Race condition in the kernel in Microsoft Windows XP SP3 allows local users to gain privileges via vectors involving thread creation, aka "…

published 2010-08-11 16y ago modified 2026-06-16 4mo ago also EUVD-2010-1907

cvss: 6.8; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.5%; EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits: 1; Exploit-DB

Race condition in the kernel in Microsoft Windows XP SP3 allows local users to gain privileges via vectors involving thread creation, aka "Windows Kernel Data Initialization Vulnerability."

Is CVE-2010-1888 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 Fencer

Timeline

2010-08-11 Published
2010-08-17 First public exploit (EDB-14666)

Exploit prediction

2.50% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

EDB-14666 Microsoft Windows - nt!NtCreateThread Race Condition with Invalid Code Segment (MS10-047) dos, 2010-08-17

CVSS scores

assigned by	version	score	vector
NVD	2.0	6.8	AV:L/AC:L/Au:S/C:C/I:C/A:C

Classification

Weakness

CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

docs.microsoft.com /en-us/security-updates/securitybulletins/2010/ms10-047
vendor-advisory
us-cert.gov /cas/techalerts/TA10-222A.html
third-party-advisory, us-government-resource
oval.cisecurity.org /repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11825
vdb-entry, signature

Sources

CVE List CVE-2010-1888
NVD CVE-2010-1888

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.