CVE-2026-89784

CVE CVE-2026-89784EUVD EUVD-2026-80305Published 2026-09-16T08:48:22.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6 rpcb_register_inet4() and rpcb_register_inet6() store the result of rpc_sockaddr2uaddr() into map->r_addr without checking it for NULL. rpc_sockaddr2uaddr() returns NULL when its final kstrdup() fails, and the unchecked NULL is then carried into the synchronous RPCBPROC_SET encode path: rpcb_register_call() -> rpc_call_sync() -> rpcb_enc_getaddr() -> encode_rpcb_string(), whose first statement is strlen(string), dereferencing NULL and oopsing the kernel. The crash reproduces under failslab on v6.12; with KASAN the NULL dereference surfaces as a fault on the shadow of address zero: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000 [#1] PREEMPT SMP KASAN RIP: 0010:strlen (lib/string.c:409) Call Trace: encode_rpcb_string (net/sunrpc/rpcb_clnt.c:890) rpcb_enc_getaddr (net/sunrpc/rpcb_clnt.c:910) rpcauth_wrap_req_encode (net/sunrpc/auth.c:745) call_encode (net/sunrpc/clnt.c:1966) __rpc_execute (net/sunrpc/sched.c:952) rpc_run_task (net/sunrpc/clnt.c:1243) rpc_call_sync (net/sunrpc/clnt.c:1272) rpcb_v4_register (net/sunrpc/rpcb_clnt.c:500) svc_generic_rpcbind_set nfsd_rpcbind_set svc_register svc_setup_socket svc_addsock write_ports nfsctl_transaction_write vfs_write The crash is reachable when an in-kernel RPC service (nfsd, lockd, nfs-callback) registers with the local rpcbind under enough memory pressure for the small GFP_KERNEL kstrdup() in rpc_sockaddr2uaddr() to fail. The asynchronous getport path already handles this exact failure mode by returning -ENOMEM; only the two register helpers omit the check. Mirror that handling: bail out with -ENOMEM when rpc_sockaddr2uaddr() returns NULL, before the address is fed into the encoder.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux d77385f23830ee6c400569bac8b37e6eb3b7d360 <4e01022974355732e748ec8ebc97c558cb624ffe; patch: 7.3-rc1; d77385f23830ee6c400569bac8b37e6eb3b7d360 <eb476289c12cc22c8766f8a84eeb7ab46c4e8fb6; patch: 0; patch: 7.2.6; patch: 6.1.188; d77385f23830ee6c400569bac8b37e6eb3b7d360 <04441b792ec40eb66349b5fab34b6a2090b5b2dd; d77385f23830ee6c400569bac8b37e6eb3b7d360 <cda4aacfb0bbf5c0f90fd0b42c72c749635d1368; 3.2; patch: 5.10.270; patch: 6.6.157; patch: 6.18.52; d77385f23830ee6c400569bac8b37e6eb3b7d360 <12bf3e0182ccdaf3b412756a756d3944a7dacaa9; patch: 5.15.221; d77385f23830ee6c400569bac8b37e6eb3b7d360 <fd22370226a0d8109045d0831fd5aaadee921693; d77385f23830ee6c400569bac8b37e6eb3b7d360 <5a51c49ddb37b883566874aecc66bc5a2e617a96; patch: 6.12.110; d77385f23830ee6c400569bac8b37e6eb3b7d360 <4a6095de8cb1858e05bdf70b3e7d6d7645c25041

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.