Under certain conditions, the Linux kernel may become tainted. For example, loading a proprietary video driver into the kernel taints the kernel. This condition may be visible in system logs, kernel error messages (oops and panics), and through tools such as lsmod, and remains until the system is rebooted.

What does this mean? Does it affect my ability to use the system, and how might it affect my support options?

  • possible duplicate of lsmod outputs: Not tainted – Gilles Mar 4 '14 at 23:51
  • @Gilles, I think the question you linked to should be merged into this one. Also, it's not obvious that one question is a duplicate of the other. – bwDraco Mar 4 '14 at 23:55
  • I'm hoping to make this the canonical version of the question; see the most recent edit to the question. – bwDraco Mar 5 '14 at 0:06
  • 9
    @MichaelMrozek: 1) I didn't see the existing question, since it wasn't obvious that the user was asking "what does 'tainted' mean", and 2) the question as worded is rather specific to a single command, lsmod. I wrote this question and answer to make it more general so that someone asking "what does 'tainted' mean" can find it easily. – bwDraco Mar 5 '14 at 0:26
  • 1
    They could have used a word that was a bit more neutral than "tainted". – Roger Dahl Nov 10 '18 at 18:08

When the kernel is tainted, it means that it is in a state that is not supported by the community. Most kernel developers will ignore bug reports involving tainted kernels, and community members may ask that you correct the tainting condition before they can proceed with diagnosing problems related to the kernel. In addition, some debugging functionality and API calls may be disabled when the kernel is tainted.

In most cases involving proprietary drivers, you can safely ignore the taint condition, but some scenarios which cause the kernel to become tainted may be indicative of serious system problems.

The feature is intended to identify conditions which may make it difficult to properly troubleshoot a kernel problem. For example, the loading of a proprietary module can make kernel debug output unreliable because kernel developers don't have access to the module's source code and therefore cannot determine what the module may have done to the kernel. Likewise, if the kernel had previously experienced an error condition or if a serious hardware error had occurred, the debug information generated by the kernel may not be reliable.

The kernel may become tainted for any of several reasons, including (but not limited to) the following:

  • The use of a proprietary (or non-GPL-compatible) kernel module—this is the most common cause of tainted kernels and usually results from loading proprietary NVIDIA or AMD video drivers
  • The use of staging drivers, which are part of the kernel source code but are not fully tested
  • The use of out-of-tree modules that are not included with the Linux kernel source code
  • Forcible loading or unloading of a kernel module (such as forcibly inserting a module not built for the current version of the kernel)
  • The use of an SMP (multiprocessor) kernel on certain unsupported uniprocessor CPUs, primarily older AMD Athlon processors
  • Overriding of the ACPI DSDT, sometimes needed to correct for power-management bugs (see here for details)
  • Certain critical error conditions, such as machine check exceptions and kernel oopses
  • Certain serious bugs in the system firmware (BIOS, UEFI) which the kernel must work around

Each of these conditions is represented by a particular flag in the kernel. Some Linux vendors, such as SUSE, add additional taint flags to indicate conditions such as loading a module that is not supported by the vendor.

More information is available in the kernel documentation. The taint flags listed there are (with _ a stand-in for 'blank')

  • G|P : G if all modules loaded have a GPL or compatible license, otherwise a proprietary module has been loaded. Modules without a MODULE_LICENSE or with a MODULE_LICENSE that is not recognised by insmod as GPL compatible are assumed to be proprietary.
  • F|_ : if any module was force loaded by "insmod -f" otherwise if all modules were loaded normally.
  • S|_ : if the oops occurred on an SMP kernel running on hardware that hasn't been certified as safe to run multiprocessor. Currently this occurs only on various Athlons that are not SMP capable.
  • R|_ : if a module was force unloaded by rmmod -f, otherwise if all modules were unloaded normally.
  • M|_ : if any processor has reported a Machine Check Exception, otherwise no Machine Check Exceptions have occurred.
  • B|_ : if a page-release function has found a bad page reference or some unexpected page flags.
  • U|_ : if a user or user application specifically requested that the Tainted flag be set.
  • D|_ : if the kernel has died recently, i.e. there was an OOPS or BUG.
  • A|_ : if the ACPI table has been overridden.
  • W|_ : if a warning has previously been issued by the kernel (Though some warnings may set more specific taint flags.)
  • C|_ : if a staging driver has been loaded.
  • I|_ : if the kernel is working around a severe bug in the platform firmware (BIOS or similar).
  • O|_ : if an externally-built ("out-of-tree") module has been loaded.
  • E|_ : if an unsigned module has been loaded in a kernel supporting module signature.
  • L|_ : if a soft lockup has previously occurred on the system.
  • K|_ : if the kernel has been live patched.
  • This answer is missing a lot of information from the dup this question displaced. – jww Jun 3 '18 at 15:51
  • I would add at least one important possibility of the "unsigned module" scenario -- a kernel rootkit was loaded into the kernel or kernel exploit was just executed. – kravietz Dec 8 '18 at 22:47

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.