linux-kernel - Re: [PATCH] kernel-chktaint: add reporting for tainted modules

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <892775bd-401d-46df-a730-a4f9a09f5149@infradead.org>
Date: Tue, 28 Oct 2025 12:51:44 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Thorsten Leemhuis <linux@...mhuis.info>, linux-kernel@...r.kernel.org
Cc: Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org
Subject: Re: [PATCH] kernel-chktaint: add reporting for tainted modules



On 10/28/25 3:05 AM, Thorsten Leemhuis wrote:
> On 10/28/25 08:12, Randy Dunlap wrote:
>> Check all loaded modules and report any that have their 'taint'
>> flags set along with a count of all tainted modules.
>> The tainted module output format is:
>> <module_name>: taint=<flags>
>>
>> Example output:
>>
>> Kernel is "tainted" for the following reasons:
>>  * externally-built ('out-of-tree') module was loaded  (#12)
>>  * unsigned module was loaded (#13)
>> Raw taint value as int/string: 12288/'G           OE      '
> 
> I wonder if it would be easier more readable if the format used above...
>> Modules tainted: count=1
>> dump_test: taint=OE
> 
> ...would be reused here somewhat. Like this maybe?
> 
> Modules tainted: 1
>  * dump_test (OE)

Yeah, I like that. Thanks.

-- 
~Randy