{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89700 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89700 is a memory corruption vulnerability in Linux, published on 11 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-89700 and fix it if it is affected.\n\nWhat it is: CVE-2026-89700 is a memory corruption vulnerability in Linux, published on 11 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-89700 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-89700/ (Markdown: https://insights.sbomify.com/CVE-2026-89700/index.md)","id":"CVE-2026-89700","markdown":"https://insights.sbomify.com/CVE-2026-89700/index.md","name":"CVE-2026-89700","record":{"aliases":["BELL-CVE-2026-89700","DEBIAN-CVE-2026-89700","GHSA-wm2v-r9v6-53mg","UBUNTU-CVE-2026-89700"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NFS","requires_auth":"high_privilege","summary":"A local attacker with CAP_NET_ADMIN can trigger an out-of-bounds read in the Linux kernel NFS daemon by sending malformed socket address data.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nnfsd: validate sockaddr length per family in listener_set\n\nnfsd_sock_nl_policy declares NFSD_A_SOCK_ADDR as a bare NLA_BINARY\nattribute with no minimum length. A CAP_NET_ADMIN caller can send a\n16-byte NFSD_A_SOCK_ADDR with sa_family=AF_INET6, causing a 12-byte\nOOB read across three consumers (rpc_cmp_addr_port, svc_find_listener,\nkernel_bind).\n\nnfsd_nl_listener_set_doit() also parsed and validated each listener\nentry inline in two separate loops, interleaved with mutating the\nrunning listener configuration. The validation was duplicated, used an\nopen-coded \"nla_len \u003c sizeof(struct sockaddr)\" check that was too short\nfor AF_INET6, and handled a malformed entry inconsistently depending on\nwhich loop noticed it.\n\nAdd an nfsd_nl_validate_listeners() helper that walks the entire list\nonce and confirms each entry parses, carries both an address and a\ntransport name, and is long enough for its address family\n(sizeof(struct sockaddr_in) for AF_INET, sizeof(struct sockaddr_in6)\nfor AF_INET6, -EAFNOSUPPORT otherwise). Call it before taking\nnfsd_mutex or creating the serv, so a malformed request fails cleanly\nwith no side effects.\n\nSince every entry is known valid by the time the two existing loops\nrun, drop the redundant presence and per-family length checks from\nboth, leaving only the nla_parse_nested() call needed to extract the\ndata.","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":"nfsd: validate sockaddr length per family in listener_set","id":"CVE-2026-89700","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"nfsd: validate nseconds in TIME_DELEG decode paths","id":"CVE-2026-89701"},"packages":[],"prev":{"headline":"nfsd: validate symlink target length in NFSv4 CREATE","id":"CVE-2026-89699"},"products":["Linux"],"published":"2026-09-11","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 local attacker with CAP_NET_ADMIN can trigger an out-of-bounds read in the Linux kernel NFS daemon by sending malformed socket address data.","url":"https://insights.sbomify.com/CVE-2026-89700/"}