GHSA-HF6G-M6V3-8GJ5
Vulnerability from github – Published: 2025-10-01 12:30 – Updated: 2025-10-01 12:30In the Linux kernel, the following vulnerability has been resolved:
nfs: fix possible null-ptr-deref when parsing param
According to commit "vfs: parse: deal with zero length string value", kernel will set the param->string to null pointer in vfs_parse_fs_string() if fs string has zero length.
Yet the problem is that, nfs_fs_context_parse_param() will dereferences the param->string, without checking whether it is a null pointer, which may trigger a null-ptr-deref bug.
This patch solves it by adding sanity check on param->string in nfs_fs_context_parse_param().
{
"affected": [],
"aliases": [
"CVE-2022-50455"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-10-01T12:15:38Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfs: fix possible null-ptr-deref when parsing param\n\nAccording to commit \"vfs: parse: deal with zero length string value\",\nkernel will set the param-\u003estring to null pointer in vfs_parse_fs_string()\nif fs string has zero length.\n\nYet the problem is that, nfs_fs_context_parse_param() will dereferences the\nparam-\u003estring, without checking whether it is a null pointer, which may\ntrigger a null-ptr-deref bug.\n\nThis patch solves it by adding sanity check on param-\u003estring\nin nfs_fs_context_parse_param().",
"id": "GHSA-hf6g-m6v3-8gj5",
"modified": "2025-10-01T12:30:28Z",
"published": "2025-10-01T12:30:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-50455"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/46819f604557fe7bc39a6c352fd368371aa9cd6e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/55513864b418c6453d68aebc36cffcf965342426"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5559405df652008e56eee88872126fe4c451da67"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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.