Kernel mods stopped working. Getting "disagrees about version of symbol" errors

Hello, I am trying to add kernel modules in my yocto build like overlay_fs. This was working fine at some point. I have no idea what I happened, but I am not able to get the kernel modules to load anymore. lsmod comes up empty and all modules in dmesg error with “unknown symbol (error -22)” and “disagrees about version of symbol”.
I normally delete the build folder, but I also tried bitbake -c cleanall <image> without success.
Below are a few different outputs for commands I have tried for debugging:

root@apalis-imx8-14715993:~# lsmod
Module                  Size  Used by
v4l2_jpeg              16384  0
root@apalis-imx8-14715993:~# zcat /proc/config.gz | grep OVERLAY_FS
# CONFIG_OVERLAY_FS is not set
root@apalis-imx8-14715993:~# modprobe -v overlay
insmod /lib/modules/5.15.129-6.4.0-devel+git.67c3153d20ff/kernel/fs/overlayfs/overlay.ko 
modprobe: ERROR: could not insert 'overlay': Invalid argument
root@apalis-imx8-14715993:~# modinfo overlay
filename:       /lib/modules/5.15.129-6.4.0-devel+git.67c3153d20ff/kernel/fs/overlayfs/overlay.ko
alias:          fs-overlay
license:        GPL
description:    Overlay filesystem
author:         Miklos Szeredi <miklos@szeredi.hu>
depends:        
intree:         Y
name:           overlay
vermagic:       5.15.129-6.4.0-devel+git.67c3153d20ff SMP preempt mod_unload modversions aarch64
parm:           check_copy_up:Obsolete; does nothing
parm:           redirect_max:Maximum length of absolute redirect xattr value (ushort)
parm:           redirect_dir:Default to on or off for the redirect_dir feature (bool)
parm:           redirect_always_follow:Follow redirects even if redirect_dir feature is turned off (bool)
parm:           index:Default to on or off for the inodes index feature (bool)
parm:           nfs_export:Default to on or off for the NFS export feature (bool)
parm:           xino_auto:Auto enable xino feature (bool)
parm:           metacopy:Default to on or off for the metadata only copy up feature (bool)
root@apalis-imx8-14715993:~# dmesg | grep overlay
[  194.096477] overlay: disagrees about version of symbol vfs_rename
[  194.102685] overlay: Unknown symbol vfs_rename (err -22)
[  194.108311] overlay: disagrees about version of symbol lookup_one_len
[  194.114798] overlay: Unknown symbol lookup_one_len (err -22)
[  194.120649] overlay: disagrees about version of symbol generic_permission
[  194.127459] overlay: Unknown symbol generic_permission (err -22)
[  194.133556] overlay: disagrees about version of symbol vfs_unlink
[  194.139670] overlay: Unknown symbol vfs_unlink (err -22)
[  194.145053] overlay: disagrees about version of symbol path_put
[  194.151041] overlay: Unknown symbol path_put (err -22)
[  194.156285] overlay: disagrees about version of symbol vfs_mkdir
[  194.162318] overlay: Unknown symbol vfs_mkdir (err -22)
[  194.167766] overlay: disagrees about version of symbol vfs_get_link
[  194.174058] overlay: Unknown symbol vfs_get_link (err -22)
[  194.179622] overlay: disagrees about version of symbol lock_rename
[  194.185822] overlay: Unknown symbol lock_rename (err -22)
[  194.191316] overlay: disagrees about version of symbol kern_path
[  194.197356] overlay: Unknown symbol kern_path (err -22)
[  194.202636] overlay: disagrees about version of symbol unlock_rename
[  194.209020] overlay: Unknown symbol unlock_rename (err -22)
[  194.214628] overlay: disagrees about version of symbol vfs_rmdir
[  194.220671] overlay: Unknown symbol vfs_rmdir (err -22)
[  194.225980] overlay: disagrees about version of symbol vfs_symlink
[  194.232191] overlay: Unknown symbol vfs_symlink (err -22)
[  194.237669] overlay: disagrees about version of symbol vfs_mknod
[  194.243702] overlay: Unknown symbol vfs_mknod (err -22)
[  194.248971] overlay: disagrees about version of symbol lookup_positive_unlocked
[  194.256309] overlay: Unknown symbol lookup_positive_unlocked (err -22)
[  194.262927] overlay: disagrees about version of symbol lookup_one_len_unlocked
[  194.270184] overlay: Unknown symbol lookup_one_len_unlocked (err -22)
[  194.276685] overlay: disagrees about version of symbol rcuwait_wake_up
[  194.283244] overlay: Unknown symbol rcuwait_wake_up (err -22)
[  194.289036] overlay: disagrees about version of symbol vfs_tmpfile
[  194.295248] overlay: Unknown symbol vfs_tmpfile (err -22)
[  194.300685] overlay: disagrees about version of symbol vfs_link
[  194.306637] overlay: Unknown symbol vfs_link (err -22)
[  194.311832] overlay: disagrees about version of symbol inode_permission
[  194.318483] overlay: Unknown symbol inode_permission (err -22)
[  194.324389] overlay: disagrees about version of symbol vfs_create
[  194.330510] overlay: Unknown symbol vfs_create (err -22)
[  993.102143] overlay: disagrees about version of symbol vfs_rename
[  993.108607] overlay: Unknown symbol vfs_rename (err -22)
[  993.114017] overlay: disagrees about version of symbol lookup_one_len
[  993.120543] overlay: Unknown symbol lookup_one_len (err -22)
[  993.126376] overlay: disagrees about version of symbol generic_permission
[  993.133222] overlay: Unknown symbol generic_permission (err -22)
[  993.139335] overlay: disagrees about version of symbol vfs_unlink
[  993.145464] overlay: Unknown symbol vfs_unlink (err -22)
[  993.150834] overlay: disagrees about version of symbol path_put
[  993.156778] overlay: Unknown symbol path_put (err -22)
[  993.161972] overlay: disagrees about version of symbol vfs_mkdir
[  993.168014] overlay: Unknown symbol vfs_mkdir (err -22)
[  993.173459] overlay: disagrees about version of symbol vfs_get_link
[  993.179764] overlay: Unknown symbol vfs_get_link (err -22)
[  993.185333] overlay: disagrees about version of symbol lock_rename
[  993.191535] overlay: Unknown symbol lock_rename (err -22)
[  993.197032] overlay: disagrees about version of symbol kern_path
[  993.203054] overlay: Unknown symbol kern_path (err -22)
[  993.208336] overlay: disagrees about version of symbol unlock_rename
[  993.214714] overlay: Unknown symbol unlock_rename (err -22)
[  993.220315] overlay: disagrees about version of symbol vfs_rmdir
[  993.226345] overlay: Unknown symbol vfs_rmdir (err -22)
[  993.231631] overlay: disagrees about version of symbol vfs_symlink
[  993.237829] overlay: Unknown symbol vfs_symlink (err -22)
[  993.243288] overlay: disagrees about version of symbol vfs_mknod
[  993.249316] overlay: Unknown symbol vfs_mknod (err -22)
[  993.254562] overlay: disagrees about version of symbol lookup_positive_unlocked
[  993.261895] overlay: Unknown symbol lookup_positive_unlocked (err -22)
[  993.268510] overlay: disagrees about version of symbol lookup_one_len_unlocked
[  993.275754] overlay: Unknown symbol lookup_one_len_unlocked (err -22)
[  993.282229] overlay: disagrees about version of symbol rcuwait_wake_up
[  993.288779] overlay: Unknown symbol rcuwait_wake_up (err -22)
[  993.294554] overlay: disagrees about version of symbol vfs_tmpfile
[  993.300755] overlay: Unknown symbol vfs_tmpfile (err -22)
[  993.306174] overlay: disagrees about version of symbol vfs_link
[  993.312116] overlay: Unknown symbol vfs_link (err -22)
[  993.317289] overlay: disagrees about version of symbol inode_permission
[  993.323922] overlay: Unknown symbol inode_permission (err -22)
[  993.329811] overlay: disagrees about version of symbol vfs_create
[  993.335940] overlay: Unknown symbol vfs_create (err -22)
root@apalis-imx8-14715993:~# 

Thanks in advance!

I was modifying the kernel in my rootfs /boot partition mmcblk0p2, but the bootloader was loading the kernel on mmcblk0p1. To solve this, I removed CORE_IMAGE_EXTRA_INSTALL += " kernel-image kernel-devicetree" from my local.conf and modified my software update mechanism to update both partitions.