How to unload a kernel module in Linux

Unloading a kernel module lets a running Linux system stop using a driver or kernel feature without a reboot, which is useful during driver testing, device troubleshooting, and cleanup after a temporary module is no longer needed.

Linux keeps loadable modules separate from the core kernel image and tracks them in /proc/modules. The lsmod command formats that live module table, including each module's size and current Used by count, while modprobe –remove asks kmod to remove a module through its normal dependency rules and dependency metadata.

Unloading a module usually requires sudo, and it works only when nothing is still holding the module in use. Storage, network, graphics, and virtualization drivers can drop live services or access paths when removed, and some features are built directly into the running kernel instead of shipped as removable modules, so confirm the correct module name and plan the change during a safe maintenance window before unloading anything critical.

1. Review the current loaded-module table and locate the target module name before removing anything.

   $ lsmod
   Module                  Size  Used by
   bridge                421888  1 br_netfilter
   dummy                  12288  0
   nf_tables             380928  0
   ##### snipped #####

   Look for the target in the first column. The Used by field shows the current reference count followed by dependent module names, so a nonzero value usually means something is still holding the module open.

2. Preview the dependency-aware removal path before making the change.

   $ modprobe --dry-run --verbose --remove dummy
   rmmod dummy

   modprobe uses the current module dependency data to remove unused prerequisite modules automatically, and it treats hyphens and underscores as the same module name.

3. Unload the module after the dry run looks correct.

   $ sudo modprobe --remove dummy

   A successful unload normally prints no output.

   Do not unload the storage, network, display, or virtualization module that keeps the current system reachable unless the maintenance plan already accounts for the outage.

4. Confirm that the module directory is gone from /sys/module after removal.

   $ ls /sys/module/dummy
   ls: cannot access '/sys/module/dummy': No such file or directory

   Use the exact module name shown by lsmod. If the directory still exists, the module is still active or was loaded again immediately by userspace.

5. Inspect the module's holders when the unload fails because another module still depends on it.

   $ ls /sys/module/videobuf2_memops/holders
   videobuf2_vmalloc

   Each name under /sys/module/<module>/holders is a dependent module that still needs the target. Stop the related service, detach the device, or unload the dependent module first, then retry the original removal command.

6. Retrying removal while the module is still busy returns an in-use error.

   $ sudo modprobe --remove videobuf2_memops
   modprobe: FATAL: Module videobuf2_memops is in use.

   Do not switch to forced removal as a routine fix. rmmod –force works only on kernels built with force-unload support and can destabilize the running system by removing a module that still owns active resources.

7. If the driver works but never appears in lsmod, check whether it is built into the running kernel instead of being a removable module.

   $ modinfo loop
   name:           loop
   filename:       (builtin)
   ##### snipped #####

   A filename: (builtin) result means the feature is compiled into the kernel image, so it cannot be unloaded with modprobe –remove.