kernel message being thrown to open console

Since upgrading my RHEL 8.5 environment (kernel-4.18.0-348.12.2.el8_5.x86_64) I am encountering an issue where kernel messages are thrown to an open console.

Details:
I have a guake console open. On 2/2/2022 these kernel messages began to appear in the guake console:

Message from syslogd@p1-raptor at Feb 2 05:19:01 ...
kernel:Call Trace:
Message from syslogd@p1-raptor at Feb 2 05:19:01 ...
kernel: __schedule+0x2bd/0x760
Message from syslogd@p1-raptor at Feb 2 05:19:01 ...
kernel: ? lock_timer_base+0x67/0x80
....

A check of the journal shows there was a blocked thread at this time:
Feb 02 05:19:01 p1-raptor kernel: INFO: task blkid:1664174 blocked for more than 120 seconds.
Feb 02 05:19:01 p1-raptor kernel: Tainted: P OE --------- - - 4.18.0-348.12.2.el8_5.x86_64 #1
Feb 02 05:19:01 p1-raptor kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 02 05:19:01 p1-raptor kernel: task:blkid state:D stack: 0 pid:1664174 ppid:1664173 flags:0x00000080
Feb 02 05:19:01 p1-raptor kernel: Call Trace:
Feb 02 05:19:01 p1-raptor kernel: __schedule+0x2bd/0x760
Feb 02 05:19:01 p1-raptor kernel: ? lock_timer_base+0x67/0x80

The console messages continued until 05:37:27, when the thread was no longer being reported as block. The obvious thing here is to take an action that will result in these blocked thread messages not generating kernel message.

But the real question is why are these messages being thrown to the console after an upgrade to the kernel-4.18.0-348.12.2.el8_5.x86_64.

Current printk setting blocks messages:
cat /etc/sysctl.d/kernel-messages.conf
kernel.printk = 0 0 0 0

cat /proc/sys/kernel/printk
0 0 0 0

I upgraded to kernel-4.18.0-348.12.2.el8_5.x86_64 on Jan. 26, 2021 and have seen this issue multiple times since the upgrade.

Is anyone else encountering this issue or does anyone have possible troubleshooting steps or even better a solution?