CVE-2010-4661 json
udisks before 1.0.3 allows a local user to load arbitrary Linux kernel modules.
published 6y ago modified 4mo ago also EUVD-2010-4626
- cvss
- 7.8
- 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 35%
- public exploits
- 0
- none known
Summary
udisks before 1.0.3 allows a local user to load arbitrary Linux kernel modules.
Patch / fix
- udisks_project udisks 1.0.3
- udisks openSUSE Tumbleweed 1.0.5-5.10
opensuse advisories openSUSE-SU-2024:10408-1
Is CVE-2010-4661 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2010-4661 updated cvss 4.6
udisks: arbitrary Linux kernel loading flaw
-
Red Hat Enterprise Linux 6 udisksaffected: no fix planned “Will not fix”
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.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- udisks udisks
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
security-tracker.debian.org
/tracker/CVE-2010-4661
third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2010-4661
issue-tracking, third-party-advisory
-
access.redhat.com
/security/cve/cve-2010-4661
third-party-advisory
-
lists.opensuse.org
/opensuse-security-announce/2011-05/msg00000.html
mailing-list, third-party-advisory
Sources
- CVE List CVE-2010-4661
- NVD CVE-2010-4661
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.