FKIE_CVE-2026-89700
Vulnerability from fkie_nvd - Published: 2026-09-11 20:19 - Updated: 2026-10-19 09:18| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/nfsd/nfsctl.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "bf85a0f1e45258f90ceeec14772b5769697dfd75",
"status": "affected",
"version": "16a471177496c8e04a9793812c187a2c1a2192fa",
"versionType": "git"
},
{
"lessThan": "2aca70c18c5f5d06004122861fb151d5fcc57faf",
"status": "affected",
"version": "16a471177496c8e04a9793812c187a2c1a2192fa",
"versionType": "git"
},
{
"lessThan": "22d0e4752ca88fd84196d22ebeedc905e6540440",
"status": "affected",
"version": "16a471177496c8e04a9793812c187a2c1a2192fa",
"versionType": "git"
},
{
"lessThan": "bdcc85c2b05a9378d8bd2d65f9fc41440a3cf464",
"status": "affected",
"version": "16a471177496c8e04a9793812c187a2c1a2192fa",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/nfsd/nfsctl.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.10"
},
{
"lessThan": "6.10",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.111",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.50",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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."
}
],
"id": "CVE-2026-89700",
"lastModified": "2026-10-19T09:18:08.657",
"metrics": {},
"published": "2026-09-11T20:19:57.187",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/22d0e4752ca88fd84196d22ebeedc905e6540440"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2aca70c18c5f5d06004122861fb151d5fcc57faf"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/bdcc85c2b05a9378d8bd2d65f9fc41440a3cf464"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/bf85a0f1e45258f90ceeec14772b5769697dfd75"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.