GHSA-VFM8-XW8F-Q53W
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 12:31In the Linux kernel, the following vulnerability has been resolved:
x86/amd_node: Fix PCI device reference counting in amd_smn_init()
The local "root" pointer is a temporary variable used during the device search. Therefore, refcount related to the search iterators should be cleaned up after the search is complete.
Use the __free() cleanup macro to ensure the refcount is decremented when the temporary pointer goes out of scope.
Additionally, increment the refcount when caching a root pointer. This ensures the in-use refcount is separate from the temporary search refcounting.
Finally, drop the redundant "root = NULL" before the second search loop. The pci_get_class() iterator always decrements the refcount of its "from" argument, so the first loop can only fall through with "root" already NULL.
{
"affected": [],
"aliases": [
"CVE-2026-97946"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:22Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/amd_node: Fix PCI device reference counting in amd_smn_init()\n\nThe local \"root\" pointer is a temporary variable used during the device\nsearch. Therefore, refcount related to the search iterators should be cleaned\nup after the search is complete.\n\nUse the __free() cleanup macro to ensure the refcount is decremented when the\ntemporary pointer goes out of scope.\n\nAdditionally, increment the refcount when caching a root pointer. This ensures\nthe in-use refcount is separate from the temporary search refcounting.\n\nFinally, drop the redundant \"root = NULL\" before the second search loop. The\npci_get_class() iterator always decrements the refcount of its \"from\"\nargument, so the first loop can only fall through with \"root\" already NULL.",
"id": "GHSA-vfm8-xw8f-q53w",
"modified": "2026-09-25T12:31:29Z",
"published": "2026-09-25T12:31:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97946"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/27600805e62f800bacf990354632eae4e487d34c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/84e3a71d11d8593c127b468d75b2653af5074f81"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/aa2a4277ad42fd8f918c6dc652473946a253f7b0"
}
],
"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.