CVE-2026-89543: sunrpc: fix use-after-free in __rpc_clnt_handle_event and __rpc_clnt_remove_pipedir
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 1a713814e0580f946196bca5e340b37991c6e8bf, 4.20, 5.11.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1a713814e0580f946196bca5e340b37991c6e8bf, 4.20, 5.11 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 11, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 17866066b8ac1cc38fb449670bc15dc9fee4b40a, 7d61d1da2ed1f682c41cae0c8d4719cdaccee5c5, dedf2a0eb9448ae73b270743e6ea9b108189df46, 194454afa6aa9d6ed74f0c57127bc8beb27c20df, 1cdb52ffd6600a37bd355d8dce58ecd03e55e618, 6.7affected
- 7749fd2dbef72a52b5c9ffdbf877691950ed4680 and later · before 1a713814e0580f946196bca5e340b37991c6e8bfaffected · git
- cc2e7ebbeb1d0601f7f3c8d93b78fcc03a95e44a and later · before f99fedfd1dbffe8d20b421c9a7d4655a135d4fcdaffected · git
- bfca5fb4e97c46503ddfc582335917b0cc228264 and later · before 59527bbfb1eabdb28e95e7c725886cc2c2899cb3affected · git
- bfca5fb4e97c46503ddfc582335917b0cc228264 and later · before e769fcde3cc73e847b1eb3acd40c04a291cb0c0caffected · git
- bfca5fb4e97c46503ddfc582335917b0cc228264 and later · before cdf7a233cb94774b0e7df42d9157077983f5022caffected · git
- bfca5fb4e97c46503ddfc582335917b0cc228264 and later · before 932a8cf6abb2b2f8677b79153a823108d8861fe2affected · git
- 6.1.64 and later · before 6.1.191affected · semver
- 6.6.3 and later · before 6.6.160affected · semver
- 4.19.318 and later · before 4.20affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89541Sep 11, 2026 · SUNRPC: harden gss_unwrap_resp_priv length checks39Monitor
- ← EarlierCVE-2026-89542Sep 11, 2026 · SUNRPC: harden gss_krb5_unwrap_v2 against short tokens39Monitor
- Later →CVE-2026-89544Sep 11, 2026 · SUNRPC: fix gssx_dec_option_array error path bugs30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1a713814e0580f946196bca5e340b37991c6e8bf | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 59527bbfb1eabdb28e95e7c725886cc2c2899cb3 | Vendor (CNA) |
| Linux Linux | 6.1.191 | Vendor (CNA) |
| Linux Linux | 6.6 | Vendor (CNA) |
| Linux Linux | 6.6.160 | Vendor (CNA) |
| Linux Linux | 932a8cf6abb2b2f8677b79153a823108d8861fe2 | Vendor (CNA) |
| Linux Linux | cdf7a233cb94774b0e7df42d9157077983f5022c | Vendor (CNA) |
| Linux Linux | e769fcde3cc73e847b1eb3acd40c04a291cb0c0c | Vendor (CNA) |
| Linux Linux | f99fedfd1dbffe8d20b421c9a7d4655a135d4fcd | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/59527bbfb1eabdb28e95e7c725886cc2c2899cb3
- git.kernel.org/stable/c/932a8cf6abb2b2f8677b79153a823108d8861fe2
- git.kernel.org/stable/c/cdf7a233cb94774b0e7df42d9157077983f5022c
- git.kernel.org/stable/c/e769fcde3cc73e847b1eb3acd40c04a291cb0c0c
- git.kernel.org/stable/c/f99fedfd1dbffe8d20b421c9a7d4655a135d4fcd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.