GHSA-GG5R-CW5W-F3JW
Vulnerability from github – Published: 2026-08-10 15:33 – Updated: 2026-08-10 15:33In the Linux kernel, the following vulnerability has been resolved:
pds_core: fix auxiliary device add/del races
Two paths add or delete the same slot (pf->vfs[vf_id].padev): a VF's pdsc_reset_done() and the PF's devlink enable_vnet/disable_vnet handler. They serialize on config_lock, but neither guards the slot under it correctly.
add() registers and stores a new auxiliary device without first checking the slot, so a second add of an already-populated slot leaks the first device. del() makes that check outside config_lock, so two concurrent dels can both pass it; the first clears the slot, and the second dereferences a NULL pointer.
Check and update the slot under config_lock in both paths.
{
"affected": [],
"aliases": [
"CVE-2026-68317"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-10T13:20:21Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\npds_core: fix auxiliary device add/del races\n\nTwo paths add or delete the same slot (pf-\u003evfs[vf_id].padev): a VF\u0027s\npdsc_reset_done() and the PF\u0027s devlink enable_vnet/disable_vnet handler.\nThey serialize on config_lock, but neither guards the slot under it\ncorrectly.\n\nadd() registers and stores a new auxiliary device without first checking\nthe slot, so a second add of an already-populated slot leaks the first\ndevice. del() makes that check outside config_lock, so two concurrent\ndels can both pass it; the first clears the slot, and the second\ndereferences a NULL pointer.\n\nCheck and update the slot under config_lock in both paths.",
"id": "GHSA-gg5r-cw5w-f3jw",
"modified": "2026-08-10T15:33:46Z",
"published": "2026-08-10T15:33:45Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68317"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/646b58b543f3bb1641e9123b75ff7799fe7b42f1"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bdeab32a7a91acd295d52a2d4ab1cc3f2da5e454"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bfa33cd513c7ceb93c5a4c30e5662acd73c0a916"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cf0ed2ba202f5c3b300ec1bf7ff0b5d555f7d518"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ef194751fed50cf3452017b63f00142a0ab40c70"
}
],
"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.