CVE-2013-7421: Low severity Canonical Ubuntu Linux vulnerability

Published Mar 4, 2013
·
Updated

A flaw was found in the way the Linux kernel's Crypto subsystem handled automatic loading of kernel modules. A local user could use this flaw to load any installed kernel module, and thus increase the attack surface of the running kernel.

Other sources

Mathias Krause reports:

Linux Kernel 2.6.38 through 3.18 are affected by a flaw in the Crypto API that allows any local user to load any installed kernel module on systems where CONFIGCRYPTOUSERAPI=y by abusing the requestmodule() call.

In the introduction of Crypto User API in the linux kernel in version 2.6.38 introduced a defect which granted userspace applications to load kernel modules on the system, by abusing the requestmodule() kernel call.

The intention was to allow applications to leverage in-kernel cryptographic functionality and load the requested module on demand.

The kernel accomplished loading algorithms by searching for the matching kernel module name provided when a user attempts to use a socket via the AFALG socket type. Initially there were no checks involved in validating the name of the module, users could provide string and the kernel would attempt to load a module by that name in the default search path for the specific version of the kernel.

The proposed fix for CVE-2013-7421 solved the issue for the simple use case, however there was an additional attack vector which by changing the string formatting any module can still be loaded.

External reference: https://lkml.org/lkml/2013/3/4/70 https://plus.google.com/+MathiasKrause/posts/PqFCo4bfrWu http://seclists.org/oss-sec/2015/q1/229

Fixed with these 3 commits: https://git.kernel.org/linus/5d26a105b5a7 https://git.kernel.org/linus/4943ba16bbc2 https://git.kernel.org/linus/3e14dcf7cb80

I have only done light testing and they seem to solve it for me.

Red Hat

The Crypto API in the Linux kernel before 3.18.5 allows local users to load arbitrary kernel modules via a bind system call for an AFALG socket with a module name in the salgname field, a different vulnerability than CVE-2014-9644.

Affected Software

13 affected componentsFixes available
redhat/kernel-rt<0:3.10.0-327.rt56.204.el7
0:3.10.0-327.rt56.204.el7
redhat/kernel<0:3.10.0-327.el7
0:3.10.0-327.el7
redhat/kernel-rt<1:3.10.0-327.rt56.170.el6
1:3.10.0-327.rt56.170.el6
Canonical Ubuntu Linux=12.04
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=14.10
Debian Debian Linux=7.0
Debian Debian Linux=8.0
Linux Linux kernel<3.18.5
Oracle Linux=5
Oracle Linux=6
Oracle Linux=7
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-1

Event History

Mar 4, 2013
CVE Published
12:00 AM
Jan 23, 2015
Data Sourced
via Red Hat·08:48 PM
DescriptionSeverityAffected Software
Mar 2, 2015
CVE Published
via MITRE·11:00 AM
Data Sourced
via MITRE·11:00 AM
Description
Jan 11, 2024
Data Sourced
via Launchpad·10:08 PM
Description
Sep 16, 2024
Data Sourced
via Ubuntu·01:04 AM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2013-7421?

The severity of CVE-2013-7421 is classified as important as it allows local users to potentially load unauthorized kernel modules.

2

How do I fix CVE-2013-7421?

To fix CVE-2013-7421, update your Linux kernel to a version that includes the security patches addressing this vulnerability.

3

Which systems are affected by CVE-2013-7421?

CVE-2013-7421 affects several Linux distributions, including specific versions of the Red Hat kernel, Ubuntu, Debian, and Oracle Linux.

4

What types of attacks can CVE-2013-7421 enable?

CVE-2013-7421 can enable local users to load kernel modules, thereby increasing the attack surface and potentially allowing privilege escalation.

5

Is there a known exploit for CVE-2013-7421?

As of now, there are no widely known exploits published for CVE-2013-7421, but users are still advised to apply security updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203