CVE-2010-4210 json
The pfs_getextattr function in FreeBSD 7.x before 7.3-RELEASE and 8.x before 8.0-RC1 unlocks a mutex that was not previously locked, which…
published 15y ago modified 4mo ago also EUVD-2010-4184
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 1
- Exploit-DB
Summary
The pfs_getextattr function in FreeBSD 7.x before 7.3-RELEASE and 8.x before 8.0-RC1 unlocks a mutex that was not previously locked, which allows local users to cause a denial of service (kernel panic), overwrite arbitrary memory locations, and possibly execute arbitrary code via vectors related to opening a file on a file system that uses pseudofs.
Patch / fix
- freebsd freebsd 7.3
Is CVE-2010-4210 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 FencerTimeline
- First public exploit (EDB-15206)
- Published
Exploit prediction
1.13% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15206 FreeBSD - 'pseudofs' Null Pointer Dereference Privilege Escalation local, 2010-10-04
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-667 Improper Locking
References
-
exploit-db.com
/exploits/15206/
exploit, third-party-advisory, vdb-entry
-
security.freebsd.org
/advisories/FreeBSD-SA-10:09.pseudofs.asc
vendor-advisory
-
vupen.com
/english/advisories/2010/2956
vdb-entry, broken-link, vendor-advisory
-
secunia.com
/advisories/42200
third-party-advisory, broken-link, vendor-advisory
-
securitytracker.com
/id?1024724
vdb-entry, broken-link, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/63218
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2010-4210
- NVD CVE-2010-4210
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.