Re: [cip-dev] v4.19.325-cip133 pipeline failure question

[Pavel Machek <pavel@nabladev.com>]

[-- Attachment #1: Type: text/plain, Size: 3934 bytes --]

Hi!

> I noticed that one of the tests in the pipeline for v4.19.325-cip133 shows
> a failure that seems non-trivial:
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2558173750
> 
> In particular, it seems like a handful of specific CVE-related tests are
> failing. Is this kernel considered stable for release though? It is
> quite

If you need to run 4.19, 4.19.325-cip133 is very good option.

Whether it is stable/secure enough for your usecase really depends on
your usecase, and it is up to you to evaluate. Start by taking a look
at "KNOWN-BUGS" file. If you are running shell server with untrusted
users (for example), well, that a) is a bad idea and b) certainly is
very bad idea with 4.19 kernel.

Below is generic document that may give you some hints.

Best regards,
								Pavel


Good and bad ideas w.r.t. kernel and security

Kernel tries to provide many security guarantees at different
levels. Still, some things are easier to guarantee than others, and
some security barriers are really important, while others... not so
much.

Kernel should be secure against remote attackers.

    And it reasonably is, when not, we get it fixed with high priority.

Kernel should protect itself and other users against local, non-priviledged users.

    Tries, but attack surface is big.
    People don't care about DoS attacks much.
    => Running untrusted code is a bad idea. Forkbomb is few characters in sh.

Fast, out-of-order CPUs leak user data via timing side-channels. Those
CPUs should not process sensitive data. JITs can be used to extract the data.

    We can try to work around the problems and apply vendor-provided
    workarounds, but there are likely more problems in future. Similar
    bugs are hidden in CPU microarchitectures, and in particular
    Spectre workarounds are whack-a-mole and thus incomplete.
    
    Hyperthreading makes those attacks easier.
    => Use suitable CPUs to process sensitive data.

    BPF is in-kernel JIT
    => Don't use BPF, make sure it is disabled on your configurations.

Filesystems are complex, robustness against malformed filesystems is hard.

    Some filesystems try to be robust against filesystems corruption,
    and some don't even try. Some perform checks during mount, but
    that means that malicious device can work around them.

    => Don't mount untrusted filesystems. If you have to, use simple and
    common filesystem. VFAT might be good choice.
    
Kernel should protect itself against local users with CAP_XX.

    Yes, there's capability system, and in theory capabilities should be separated.
    => Don't rely on that. Noone else does.

Some systems try to protect themselves against people with physical access.

    Laws of physics says it is impossible, but people can still try to
    make it more costly for the "attacker".
    => Please don't rely on that.

Coredumps are useful for debugging, but random processes leaving files in cwd
may not be welcome

    Consider disabling coredumps, perhaps with RLIMIT_CORE=0.

    Consider putting all coredumps into single directory with /proc/sys/kernel/core_pattern.

io_uring is rather new and buggy

    https://www.phoronix.com/news/Linux-6.6-sysctl-IO_uring

Kernel config options for hardened kernel

Investigate:

CONFIG_X86_IOPL_IOPERM=y

https://timesys.com/security/securing-your-linux-configuration-kernel-hardening/

RETPOLINE=Y
DEVMEM=is not set
PAGE_POISONING=Y , enable withpage_poison=1
GCC_PLUGIN_STACKLEAK=Y
DEBUG_BUGVERBOSE=is not set , kind of security by obscurity, but may make attackers work harder; will also make your own debugging harder, so..
ARCH_HAS_ELF_RANDOMIZE=Y
INIT_ON_FREE_DEFAULT_ON=Y
INIT_ON_ALLOC_DEFAULT_ON=Y
DEBUG_VIRTUAL=Y


https://github.com/a13xp0p0v/kconfig-hardened-check ?

Unloading modules is hard and rarely used.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]