CVE-2026-89543

sunrpc: fix use-after-free in __rpc_clnt_handle_event and __rpc_clnt_remove_pipedir

N/A
Published: September 11, 2026 at 07:44 PM UTC
Updated: October 21, 2026 at 01:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

17866066b8ac1cc38fb449670bc15dc9fee4b40a194454afa6aa9d6ed74f0c57127bc8beb27c20df1cdb52ffd6600a37bd355d8dce58ecd03e55e6184.19.3185.10.2025.15.1405.4.2806.1.646.5.136.6.36.77749fd2dbef72a52b5c9ffdbf877691950ed46807d61d1da2ed1f682c41cae0c8d4719cdaccee5c5bfca5fb4e97c46503ddfc582335917b0cc228264cc2e7ebbeb1d0601f7f3c8d93b78fcc03a95e44adedf2a0eb9448ae73b270743e6ea9b108189df46
Vendor states this is fixed in 59527bbfb1eabdb28e95e7c725886cc2c2899cb3 (fixed)
Vendor states this is fixed in 932a8cf6abb2b2f8677b79153a823108d8861fe2 (fixed)
Vendor states this is fixed in cdf7a233cb94774b0e7df42d9157077983f5022c (fixed)
Vendor states this is fixed in e769fcde3cc73e847b1eb3acd40c04a291cb0c0c (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.6, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.160 (unaffected)
Vendor states this is fixed in 6.7 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card