CVE-2011-2910 json
The AX.25 daemon (ax25d) in ax25-tools before 0.0.8-13 does not check the return value of a setuid call.
published 2019-11-15 6 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2883
- cvss
- 6.7
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
The AX.25 daemon (ax25d) in ax25-tools before 0.0.8-13 does not check the return value of a setuid call. The setuid call is responsible for dropping privileges but if the call fails the daemon would continue to run with root privileges which can allow possible privilege escalation.
Patch / fix
- linux-ax25 ax25-tools 0.0.8-13
- ax25-tools Debian 13, Debian 12 0.0.8-13.2
debian advisories DEBIAN-CVE-2011-2910
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2011-2910 updated cvss 5.1
ax25-tools: possible privilege escalation due to failure to check for s*id return values
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/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 |
Affected products
- ax25-tools ax25-tools
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
security-tracker.debian.org
/tracker/CVE-2011-2910
third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2011-2910
issue-tracking, third-party-advisory
-
access.redhat.com
/security/cve/cve-2011-2910
broken-link
Sources
- CVE List CVE-2011-2910
- NVD CVE-2011-2910
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.