CVE-2006-6275 sun: Race Condition
sun: no CVSS score yet. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
Race condition in the kernel in Sun Solaris 8 through 10 allows local users to cause a denial of service (panic) via unspecified vectors, possibly related to the exitlwps function and SIGKILL and /proc PCAGENT signals.
- EPSS
- 0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
- OWASP Top 10
- A06:2025 Insecure Design
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Vendor advisory: http://secunia.com/advisories/23187
- Vendor advisory: http://www.vupen.com/english/advisories/2006/4792
Ask an AI about this CVE
Show the prompt
Explain CVE-2006-6275 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2006-6275?via=ask-ai-copy and https://cve.bz/cve/CVE-2006-6275?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2006-6275 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| sun:solaris | 8.0 |
| sun:solaris | 9.0 |
| sun:solaris | 10.0 |
| sun:sunos | 5.8 |
Attack patterns (CAPEC)
- CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
- CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
References
- http://secunia.com/advisories/23187
- http://www.vupen.com/english/advisories/2006/4792
- http://securitytracker.com/id?1017321
- http://sunsolve.sun.com/search/document.do?assetkey=1-26-102574-1
- http://www.securityfocus.com/bid/21372
- https://exchange.xforce.ibmcloud.com/vulnerabilities/30637
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1626