Comment # 52 on bug 1182666 from B

Did some more digging, looking at the rpm scripts in kernel-default there
doesn't seem to be anything that would manipulate /lib/modules/$kernel/updates/
directory so I tried removing kernel-default with the rpm tool with verbose
output:

> sudo rpm -eh -vv kernel-default-5.11.4-1.3.x86_64
*** removed part of output ***
D: %postun(kernel-default-5.11.4-1.3.x86_64): waitpid(18562) rc 18562 status 0
D: Plugin: calling hook scriptlet_post in syslog plugin
D: %triggerpostun(nvidia-gfxG05-kmp-default-460.56_k5.10.16_1-35.1.x86_64):
scriptlet start
fdio:       2 writes,      172 total bytes in 0.000011 secs
D: %triggerpostun(nvidia-gfxG05-kmp-default-460.56_k5.10.16_1-35.1.x86_64):
execv(/bin/sh) pid 19832
D: Plugin: calling hook scriptlet_fork_post in prioreset plugin
D: Plugin: calling hook scriptlet_fork_post in selinux plugin
++ find /lib/modules -mindepth 1 -maxdepth 1 -type d
+ for dir in $(find /lib/modules  -mindepth 1 -maxdepth 1 -type d)
+ '[' '!' -d /lib/modules/5.10.12-1-default/kernel ']'
+ test -d /lib/modules/5.10.12-1-default/updates
+ rm -f '/lib/modules/5.10.12-1-default/updates/nvidia*.ko'
+ for dir in $(find /lib/modules  -mindepth 1 -maxdepth 1 -type d)
+ '[' '!' -d /lib/modules/5.10.12-1khz/kernel ']'
+ for dir in $(find /lib/modules  -mindepth 1 -maxdepth 1 -type d)
+ '[' '!' -d /lib/modules/5.10.14-1-default/kernel ']'
+ test -d /lib/modules/5.10.14-1-default/updates
+ rm -f '/lib/modules/5.10.14-1-default/updates/nvidia*.ko'
+ for dir in $(find /lib/modules  -mindepth 1 -maxdepth 1 -type d)
+ '[' '!' -d /lib/modules/5.10.16-1-default/kernel ']'
+ test -d /lib/modules/5.10.16-1-default/updates
+ rm -f '/lib/modules/5.10.16-1-default/updates/nvidia*.ko'
+ for dir in $(find /lib/modules  -mindepth 1 -maxdepth 1 -type d)
+ '[' '!' -d /lib/modules/5.11.2-1-default/kernel ']'
+ test -d /lib/modules/5.11.2-1-default/updates
+ rm -f '/lib/modules/5.11.2-1-default/updates/nvidia*.ko'
+ for dir in $(find /lib/modules  -mindepth 1 -maxdepth 1 -type d)
+ '[' '!' -d /lib/modules/5.11.2-1khz/kernel ']'
+ for dir in $(find /lib/modules  -mindepth 1 -maxdepth 1 -type d)
+ '[' '!' -d /lib/modules/5.11.4-1-default/kernel ']'
+ test -d /lib/modules/5.11.4-1-default/updates
+ rm -f /lib/modules/5.11.4-1-default/updates/nvidia-drm.ko
/lib/modules/5.11.4-1-default/updates/nvidia.ko
/lib/modules/5.11.4-1-default/updates/nvidia-modeset.ko
/lib/modules/5.11.4-1-default/updates/nvidia-uvm.ko
+ for dir in $(find /lib/modules  -mindepth 1 -maxdepth 1 -type d)
+ '[' '!' -d /lib/modules/5.11.4-1-1khz/kernel ']'
*** removed part of output ***


So it seems when kernel-default is being removed the post uninstall script of
nvidia-gfxG05-kmp-default is triggered.

This looks like the right script:
> rpm -q --scripts nvidia-gfxG05-kmp-default-460.56_k5.10.16_1-35.1.x86_64
postuninstall scriptlet (using /bin/sh):
flavor=default
if [ "$1" = 0 ] ; then
    # Avoid accidental removal of G<n+1> alternative (bnc#802624)
    if [ ! -f /usr/lib/nvidia/alternate-install-present-$flavor ];  then
        /usr/sbin/update-alternatives --remove alternate-install-present
/usr/lib/nvidia/alternate-install-present-$flavor

        # get rid of *all* nvidia kernel modules when uninstalling package
(boo#1180010)
        for dir in $(find /lib/modules  -mindepth 1 -maxdepth 1 -type d); do
                test -d $dir/updates && rm -f  $dir/updates/nvidia*.ko
        done
    fi
    # cleanup of bnc# 1000625
    rm -f /usr/lib/tmpfiles.d/nvidia-logind-acl-trick-G05.conf
fi


Seems to be clear that if Nvidia kernel modules are installed before a minor
patch version kernel "upgrade" there won't be any module files after.

Also, if anyone will try to test this be careful with the rpm command, even
though I told it to erase a specific version of kernel-default for some reason
it removed all of them. Luckily I run some custom kernels and those weren't
touched.