Linux Security Modules

Short description: Framework to support computer security models

Linux Security Modules (LSM) is a framework allowing the Linux kernel to support, without bias, a variety of computer security models. LSM is licensed under the terms of the GNU General Public License and is a standard part of the Linux kernel since Linux 2.6. As of 2025,[update] AppArmor, LoadPin, SELinux, Smack, TOMOYO, Yama, SafeSetID, Integrity Policy Enforcement (IPE), and Landlock are the currently approved security modules in the official kernel.[1][2]

## Contents

* 1 Design
* 2 Adoption
* 3 History
* 4 References
* 5 External links

## Design

LSM was designed in order to answer all the requirements for successfully implementing a mandatory access control module, while imposing the fewest possible changes to the Linux kernel. LSM avoids the approach of system call interposition used by Systrace because it doesn't scale to multiprocessor kernels and is subject to TOCTTOU (race) attacks. Instead, LSM inserts "hooks" (upcalls to the module) at every point in the kernel where a user-level system-call is about to result with an access to an important internal kernel-object like inodes and process control blocks.

LSM is narrowly scoped to solve the problem of access control, while not imposing a large and complex change-patch on the mainstream kernel. It isn't intended to be a general "hook" or "upcall" mechanism, nor does it support operating system-level virtualization.

LSM's access-control goal is very closely related to the problem of system auditing, but is subtly different. Auditing requires that every attempt at access be recorded. LSM cannot deliver this, because it would require a great many more hooks, in order to detect cases where the kernel "short circuits" failing system-calls and returns an error code before getting near significant objects.

The LSM design is described in the paper "Linux Security Modules: General Security Support for the Linux Kernel"[3] presented at USENIX Security Symposium 2002.[4] At the same conference was the paper "Using CQUAL for Static Analysis of Authorization Hook Placement"[5] which studied automatic static analysis of the kernel code to verify that all of the necessary hooks have actually been inserted into the Linux kernel.

## Adoption

* AppArmor
* Integrity Policy Enforcement (IPE)[6]
* Landlock[7][8]
* LoadPin[9]
* SafeSetID[10]
* SELinux
* Smack
* TOMOYO
* Yama[11]

## History

At the 2001 Linux Kernel Summit, the NSA proposed that SELinux be included in Linux 2.5.[12] Linus Torvalds rejected SELinux at that time, because he observed that there are many different security projects in development, and since they all differ, the security community has not yet formed consensus on the ultimate security model. Instead, Linus charged the security community to "make it a module".

In response, Crispin Cowan proposed[13] LSM: an interface for the Linux kernel that provides sufficient "hooks" (upcalls) from within the Linux kernel to a loadable module so as to allow the module to enforce mandatory access controls. Development of LSM over the next two years was conducted by the LSM community, including substantial contributions from the Immunix Corporation, the NSA, McAfee, IBM, Silicon Graphics, and many independent contributors. LSM was ultimately accepted into the Linux kernel mainstream and was included as a standard part of Linux 2.6 in December 2003.

In 2006, some kernel developers observed that SELinux was the only widely used LSM module included in the mainstream Linux kernel source tree. If there is to be only one widely used LSM module, it was reasoned, then the indirection of LSM is unnecessary, and LSM should be removed and replaced with SELinux itself. However, there are other LSM modules maintained outside of the mainstream kernel tree (AppArmor, Linux Intrusion Detection System, FireFlier, CIPSO, Multi ADM, etc.), so this argument led to two results: 1. that developers of these modules started putting effort into upstreaming their respective modules, and 2. at the 2006 Linux Kernel Summit, Linus once again asserted that LSM would stay because he does not want to arbitrate which is the best security model.

LSM is likely to remain since additional security modules Smack (version 2.6.25), TOMOYO Linux (version 2.6.30, June 2009) and AppArmor (version 2.6.36) were accepted in the mainline kernel.

## References

1. ↑ "Linux Security Module Usage". The Linux Kernel documentation. https://docs.kernel.org/admin-guide/LSM/index.html.
2. ↑ "/security - Linux kernel source code". GitHub. https://github.com/torvalds/linux/tree/master/security.
3. ↑ Wright, Chris; Cowan, Crispin; Morris, James; Smalley, Stephen; Kroah-Hartman, Greg (2002). "Linux Security Modules: General Security Support for the Linux Kernel". USENIX Security '02. pp. 17-31. https://www.usenix.org/conference/11th-usenix-security-symposium/linux-security-modules-general-security-support-linux. Retrieved 2026-03-03.
4. ↑ "11th USENIX Security Symposium". USENIX. 2002. https://www.usenix.org/conference/11thusenixsecuritysymposium.
5. ↑ Zhang, Xiaolan; Edwards, Antony; Jaeger, Trent (2002). "Using CQUAL for Static Analysis of Authorization Hook Placement". USENIX Security '02. pp. 33-48. https://www.usenix.org/conference/11th-usenix-security-symposium/using-cqual-static-analysis-authorization-hook-placement. Retrieved 2026-03-03.
6. ↑ "Integrity Policy Enforcement (IPE)". The Linux Kernel documentation. https://docs.kernel.org/admin-guide/LSM/ipe.html.
7. ↑ Landlock: unprivileged access control
8. ↑ "Landlock LSM: kernel documentation". The Linux Kernel documentation. March 2025. https://docs.kernel.org/security/landlock.html.
9. ↑ "LoadPin". The Linux Kernel documentation. https://docs.kernel.org/admin-guide/LSM/LoadPin.html.
10. ↑ "SafeSetID". The Linux Kernel documentation. https://docs.kernel.org/admin-guide/LSM/SafeSetID.html.
11. ↑ "Yama". The Linux Kernel documentation. https://docs.kernel.org/admin-guide/LSM/Yama.html.
12. ↑ Smalley, Stephen; Fraser, Timothy; Vance, Chris. "Linux Security Modules: General Security Hooks for Linux". The Linux Kernel documentation. https://docs.kernel.org/security/lsm.html.
13. ↑ Cowan, Crispin (2001-04-10). "Linux Security Module Interface". linux-kernel@vger.kernel.org (Mailing list). Retrieved 2026-03-03.

## External links

* "Source code and project statistics". http://lsm.bkbits.net.
* SysAdmin magazine article on BSD Secure Levels
* Security Projects based on the Linux kernel

* v
* t
* e

Linux

Linux kernel|

* History
* Kernel
* Linus's law
* Linux-libre
* Linux startup process
* Linux kernel oops
* Tux
* more…

Controversies|

* Criticism of Linux
* Criticism of desktop Linux
* GNU/Linux naming controversy
* Tanenbaum–Torvalds debate
* SCO and Linux

Distributions|

* General comparison
* Distributions list
* Netbook-specific comparison
* Distributions that run from RAM
* Lightweight
* Security-focused operating system
* Proprietary software for Linux
* Package manager
* Package format
* List of software package managers

Organizations|

* LinuxChix
* Linux Counter
* Linux Documentation Project
* Linux Foundation
* Linux Mark Institute
* Linux User Group (LUG)

Adoption|

* Adopters
* Desktop
* Embedded
* Gaming
* Mobile
* Range of use

Media|

* DistroWatch
* Free Software Magazine
* Full Circle
* Linux.com
* Linux Format
* Linux Gazette
* Linux Journal
* Linux Magazine
* LinuxUser
* Ubuntu User
* Linux Outlaws
* Linux Voice
* LugRadio
* LWN.net
* Open Source For You
* Phoronix
* Revolution OS
* The Code

* Linux
* Linux kernel features
* Portal
* WikiProject

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Linux Security Modules. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Linux_Security_Modules&oldid=4350357"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template