"data leaks possible via Spectre v2 BHB attacks" and some other things in red in journalctl -b

Support
1

HI.
I watch my journalctl -b and found this:

feb 25 18:58:18 nueva-exo kernel: Spectre V2 : WARNING: Unprivileged eBPF is enabled with eIBRS on, data leaks possible via Spectre v2 BHB attacks!

this:

 ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20210730/psargs-330)
feb 25 18:58:18 nueva-exo kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
feb 25 18:58:18 nueva-exo kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20210730/psargs-330)
feb 25 18:58:18 nueva-exo kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS02._PLD due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
feb 25 18:58:18 nueva-exo kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20210730/psargs-330)
feb 25 18:58:18 nueva-exo kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS03._PLD due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
feb 25 18:58:18 nueva-exo kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20210730/psargs-330)
feb 25 18:58:18 nueva-exo kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS04._PLD due to previous error (AE_NOT_FOUND) (20210730/psparse-529)

This:

feb 25 18:58:22 nueva-exo gdm-autologin][641]: gkr-pam: couldn't unlock the login keyring.

This:

feb 25 18:58:27 nueva-exo kernel: audit: type=1334 audit(1677362307.519:151): prog-id=42 op=LOAD
feb 25 18:58:27 nueva-exo nginx[939]: 2023/02/25 18:58:27 [warn] 939#939: could not build optimal types_hash, you should increase either types_hash_max_size: 1024 or types_has>

I can fix something of this?

2

for the first one:

what do you think this means?

Where is the attack?

I, for one, have this parameter added to /etc/default/grub:
mitigations=off

there you go

… the same goes for the rest …

you assume to much … there is nothing broken that needs fixing

3

Have you checked to see if there’s a BIOS update that may address some of these issues?

Please post your system info as outlined here:

4

Search is your friend: Gnome-keyring 42.0 and autologin