Dkms status "WARNING! Diff between built and installed module"

My server information is as follows:
OS: RHEL8
GPU: P40*2
Driver Version: 550.67

and I have already installed dkms package from EPEL, which is used to automatically rebuild kernel modules when the kernel version is updated:

$ dkms --version
dkms-3.0.13

However, after my recent kernel update and subsequent system restart, the following error message appeared:

$ sudo dkms status
nvidia/550.67, 4.18.0-513.24.1.el8_9.x86_64, x86_64: installed
nvidia/550.67, 4.18.0-553.5.1.el8_10.x86_64, x86_64: installed (WARNING! Diff between built and installed module!)
nvidia/550.67, 4.18.0-553.8.1.el8_10.x86_64, x86_64: installed (WARNING! Diff between built and installed module!)(WARNING! Diff between built and installed module!)(WARNING! Diff between built and installed module!)(WARNING! Diff between built and installed module!)

and the output of the dmesg command is as follows:

$ sudo dmesg | grep -e nvidia -e gpu
[ 2.846897] nvidia: loading out-of-tree module taints kernel.
[ 2.846898] nvidia: loading out-of-tree module taints kernel.
[ 2.846913] nvidia: module license ‘NVIDIA’ taints kernel.
[ 2.846914] nvidia: module license ‘NVIDIA’ taints kernel.
[ 2.871340] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 2.871989] nvidia: disagrees about version of symbol acpi_get_handle
[ 2.871991] nvidia: Unknown symbol acpi_get_handle (err -22)
[ 2.872025] nvidia: disagrees about version of symbol efi
[ 2.872026] nvidia: Unknown symbol efi (err -22)
[ 2.935753] nvidia: disagrees about version of symbol acpi_get_handle
[ 2.935758] nvidia: Unknown symbol acpi_get_handle (err -22)
[ 2.935782] nvidia: disagrees about version of symbol efi
[ 2.935783] nvidia: Unknown symbol efi (err -22)

the nvidia bug report:
nvidia-bug-report.log.gz (213.0 KB)

The final solution:
$ sudo dkms remove -m nvidia -v 550.67 --all
$ sudo dkms install -m nvidia -v 550.67

What is the cause of this issue, and how can I ensure that the next kernel update does not encounter such an error?
Any help would be greatly appreciated. Thanks.