CVE-2026-98953devlink: fix devlink_rel reference leak when notify work is pending
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In 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.
Timeline
ID reserved
By Linux
- 28 days later
· 28 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected c137743bce02b18c1537d4681aa515f7b80bf0a8 – < 8c7830e0120e6e1f5084212fd5b79b3092496f87
- affected c137743bce02b18c1537d4681aa515f7b80bf0a8 – < 8de57bfec3825effb57fe4d25da98ec3b8fda4c6
- affected c137743bce02b18c1537d4681aa515f7b80bf0a8 – < dc2e787b5fb474241c8a6d18fdacb44adc6d571f
- affected c137743bce02b18c1537d4681aa515f7b80bf0a8 – < c5381ae1cd1481cc431c2bd79460472c6f1d3ce3
- affected 6.7
- unaffected < 6.7
- unaffected 6.12.113 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.11 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/8c7830e0120e6e1f5084212fd5b79b3092496f87 (opens in a new tab)
- https://git.kernel.org/stable/c/8de57bfec3825effb57fe4d25da98ec3b8fda4c6 (opens in a new tab)
- https://git.kernel.org/stable/c/dc2e787b5fb474241c8a6d18fdacb44adc6d571f (opens in a new tab)
- https://git.kernel.org/stable/c/c5381ae1cd1481cc431c2bd79460472c6f1d3ce3 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-108927 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98953)Record last updated .