sunrpc: fix use-after-free in __rpc_clnt_handle_event and __rpc_clnt_remove_pipedir
- 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.1.191, 6.6.160, 4.20, 5.5, 5.11, and 5 more
- 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: sunrpc: fix use-after-free in __rpc_clnt_handle_event and __rpc_clnt_remove_pipedir Normal client creation goes through rpc_setup_pipedir(), which records clnt->pipefs_sb, but the mount-event path in __rpc_clnt_handle_event() calls rpc_setup_pipedir_sb() directly and never refreshes that field. The umount path also removes the directory without clearing clnt->pipefs_sb. After a late pipefs mount or any remount, rpc_clnt_remove_pipedir() compares the current superblock against a stale pipefs_sb pointer and skips cleanup, leaving pipefs dentries whose inode private data still points at a freed rpc_clnt, leading to a potential use-after-free during subsequent rpc_info_open() or rpc_show_info() calls. Fix this by properly updating clnt->pipefs_sb upon mount events and clearing it during unmount or failure paths.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 6.1.64 · fixed in 6.1.191; From 6.6.3 · fixed in 6.6.160; From 4.19.318 · fixed in 4.20; From 5.4.280 · fixed in 5.5; From 5.10.202 · fixed in 5.11; From 5.15.140 · fixed in 5.16; From 6.5.13 · fixed in 6.6
- Linux Linux
6.7
- KernelLinux
fixed in 6.6.160; From 6.7.0 · fixed in 6.12.111; fixed in 6.18.50; From 6.13.0 · fixed in 7.2.4