nfsd: move nfsd_debugfs_init() after nfsd4_init_slabs() in init_nfsd()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.50, 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 9fe5ea760e64f04412dbed51645a0dac7220d40a · fixed in 4ae5d7490ae6a7b83b3d607f88c499f4f85e753a; From 9fe5ea760e64f04412dbed51645a0dac7220d40a · fixed in ab43ff94f5dfc2b6a080b167b69855eb7655c98b; From 9fe5ea760e64f04412dbed51645a0dac7220d40a · fixed in 2c390c8a1764d67095fe444401861fac4c049362
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4