nfsd: move nfsd_debugfs_init() after nfsd4_init_slabs() in init_nfsd()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2c390c8a1764d67095fe444401861fac4c049362, Kernel 4ae5d7490ae6a7b83b3d607f88c499f4f85e753a and Kernel ab43ff94f5dfc2b6a080b167b69855eb7655c98b.
In the Linux kernel, the following vulnerability has been resolved: nfsd: move nfsd_debugfs_init() after nfsd4_init_slabs() in init_nfsd() nfsd_debugfs_init() runs before nfsd4_init_slabs() in init_nfsd(). If the slab allocation fails, the bare "return retval" bypasses nfsd_debugfs_exit(), leaving orphan debugfs files with stale fops pointers into the freed module text. Move nfsd_debugfs_init() to after the slab init succeeds, so the early return has no debugfs state to clean up. Since debugfs is now the more recently initialized of the two, also update the unwind paths to match reverse-initialization (LIFO) order: run nfsd_debugfs_exit() before nfsd4_free_slabs() in both the init_nfsd() error path and exit_nfsd(). The nfsd debugfs files only reference module-global state and have no dependency on the slab caches, so that reordering is a cleanup with no functional change.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.16, >=9fe5ea760e64f04412dbed51645a0dac7220d40a <2c390c8a1764d67095fe444401861fac4c049362, >=9fe5ea760e64f04412dbed51645a0dac7220d40a <4ae5d7490ae6a7b83b3d607f88c499f4f85e753a, >=9fe5ea760e64f04412dbed51645a0dac7220d40a <ab43ff94f5dfc2b6a080b167b69855eb7655c98b | 2c390c8a1764d67095fe444401861fac4c049362, 4ae5d7490ae6a7b83b3d607f88c499f4f85e753a, ab43ff94f5dfc2b6a080b167b69855eb7655c98b |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket