{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89784 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89784 is a vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89784 and fix it if it is affected.\n\nWhat it is: CVE-2026-89784 is a vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89784 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-89784/ (Markdown: https://insights.sbomify.com/CVE-2026-89784/index.md)","id":"CVE-2026-89784","markdown":"https://insights.sbomify.com/CVE-2026-89784/index.md","name":"CVE-2026-89784","record":{"aliases":["AZL-101508","BELL-CVE-2026-89784","DEBIAN-CVE-2026-89784","GHSA-8jpc-3w39-9jvg","UBUNTU-CVE-2026-89784"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A missing null check in Linux kernel SUNRPC code causes a kernel crash when memory allocation fails during RPC service registration.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6\n\nrpcb_register_inet4() and rpcb_register_inet6() store the result of\nrpc_sockaddr2uaddr() into map-\u003er_addr without checking it for NULL.\nrpc_sockaddr2uaddr() returns NULL when its final kstrdup() fails, and\nthe unchecked NULL is then carried into the synchronous RPCBPROC_SET\nencode path: rpcb_register_call() -\u003e rpc_call_sync() -\u003e\nrpcb_enc_getaddr() -\u003e encode_rpcb_string(), whose first statement is\nstrlen(string), dereferencing NULL and oopsing the kernel.\n\nThe crash reproduces under failslab on v6.12; with KASAN the NULL\ndereference surfaces as a fault on the shadow of address zero:\n\n Oops: general protection fault, probably for non-canonical address\n       0xdffffc0000000000 [#1] PREEMPT SMP KASAN\n RIP: 0010:strlen (lib/string.c:409)\n Call Trace:\n  encode_rpcb_string (net/sunrpc/rpcb_clnt.c:890)\n  rpcb_enc_getaddr (net/sunrpc/rpcb_clnt.c:910)\n  rpcauth_wrap_req_encode (net/sunrpc/auth.c:745)\n  call_encode (net/sunrpc/clnt.c:1966)\n  __rpc_execute (net/sunrpc/sched.c:952)\n  rpc_run_task (net/sunrpc/clnt.c:1243)\n  rpc_call_sync (net/sunrpc/clnt.c:1272)\n  rpcb_v4_register (net/sunrpc/rpcb_clnt.c:500)\n  svc_generic_rpcbind_set\n  nfsd_rpcbind_set\n  svc_register\n  svc_setup_socket\n  svc_addsock\n  write_ports\n  nfsctl_transaction_write\n  vfs_write\n\nThe crash is reachable when an in-kernel RPC service (nfsd, lockd,\nnfs-callback) registers with the local rpcbind under enough memory\npressure for the small GFP_KERNEL kstrdup() in rpc_sockaddr2uaddr() to\nfail. The asynchronous getport path already handles this exact failure\nmode by returning -ENOMEM; only the two register helpers omit the check.\n\nMirror that handling: bail out with -ENOMEM when rpc_sockaddr2uaddr()\nreturns NULL, before the address is fed into the encoder.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6","id":"CVE-2026-89784","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"fs/ntfs3: fix out-of-bounds read of INDEX_ROOT in reparse/objid init","id":"CVE-2026-89785"},"packages":[],"prev":{"headline":"xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full","id":"CVE-2026-89783"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A missing null check in Linux kernel SUNRPC code causes a kernel crash when memory allocation fails during RPC service registration.","url":"https://insights.sbomify.com/CVE-2026-89784/"}