GHSA-5648-X8RM-28P3
Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31In the Linux kernel, the following vulnerability has been resolved:
devlink: fix devlink_rel reference leak when notify work is pending
devlink_rel_nested_in_notify_work_schedule() takes a reference on the devlink_rel for the notify work and then queues the work, ignoring the return value of schedule_delayed_work(). If the work is already pending, nothing new is queued, the work runs only once and drops only one reference, so the extra one is leaked together with the devlink_rel and its index in devlink_rels.
This is easy to hit. devl_register() of a nested instance queues the work, and if the instance is unregistered before the work has run, devlink_rel_put() queues it again while it is still pending. The work also keeps rescheduling itself for as long as the parent devlink lock cannot be taken, which widens the window. Registering and unregistering a nested devlink instance 100 times while holding the parent lock leaks all 100 devlink_rel objects.
The reschedule path in devlink_rel_nested_in_notify_work() has the same problem: if the work was queued again while it was running, the reference it holds is never dropped.
Drop the reference in both places when the work was already pending. The pending work holds its own reference, so this can not be the last one.
{
"affected": [],
"aliases": [
"CVE-2026-98953"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T13:17:16Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: fix devlink_rel reference leak when notify work is pending\n\ndevlink_rel_nested_in_notify_work_schedule() takes a reference on the\ndevlink_rel for the notify work and then queues the work, ignoring the\nreturn value of schedule_delayed_work(). If the work is already pending,\nnothing new is queued, the work runs only once and drops only one\nreference, so the extra one is leaked together with the devlink_rel and\nits index in devlink_rels.\n\nThis is easy to hit. devl_register() of a nested instance queues the\nwork, and if the instance is unregistered before the work has run,\ndevlink_rel_put() queues it again while it is still pending. The work\nalso keeps rescheduling itself for as long as the parent devlink lock\ncannot be taken, which widens the window. Registering and unregistering\na nested devlink instance 100 times while holding the parent lock leaks\nall 100 devlink_rel objects.\n\nThe reschedule path in devlink_rel_nested_in_notify_work() has the same\nproblem: if the work was queued again while it was running, the\nreference it holds is never dropped.\n\nDrop the reference in both places when the work was already pending.\nThe pending work holds its own reference, so this can not be the last\none.",
"id": "GHSA-5648-x8rm-28p3",
"modified": "2026-10-23T15:31:32Z",
"published": "2026-10-23T15:31:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98953"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8c7830e0120e6e1f5084212fd5b79b3092496f87"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8de57bfec3825effb57fe4d25da98ec3b8fda4c6"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c5381ae1cd1481cc431c2bd79460472c6f1d3ce3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dc2e787b5fb474241c8a6d18fdacb44adc6d571f"
}
],
"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.