Unknown

CVE-2026-98953 — devlink: fix devlink_rel reference leak when notify work is pending

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.

Published Oct 23, 2026 · Updated Oct 23, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.18%

ahead of 7% of scored CVEs · Oct 30, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ c137743bce02b18c1537d4681aa515f7b80bf0a8 and < 8c7830e0120e6e1f5084212fd5b79b3092496f87≥ c137743bce02b18c1537d4681aa515f7b80bf0a8 and < 8de57bfec3825effb57fe4d25da98ec3b8fda4c6≥ c137743bce02b18c1537d4681aa515f7b80bf0a8 and < dc2e787b5fb474241c8a6d18fdacb44adc6d571f≥ c137743bce02b18c1537d4681aa515f7b80bf0a8 and < c5381ae1cd1481cc431c2bd79460472c6f1d3ce3version 6.7	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 23, 2026
Affected products added · linux/linux
Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 23, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 23, 2026 · Alertas do Telegram
CVE published
Oct 23, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 23, 2026 – Oct 23, 2026
1× Official description updated · Oct 23, 2026 – Oct 23, 2026

References

4 on the record

git.kernel.org/stable/c/8de57bfec3825effb57fe4d25da98ec3b8fda4c6
NIST National Vulnerability Database
git.kernel.org/stable/c/dc2e787b5fb474241c8a6d18fdacb44adc6d571f
NIST National Vulnerability Database
git.kernel.org/stable/c/8c7830e0120e6e1f5084212fd5b79b3092496f87
NIST National Vulnerability Database
git.kernel.org/stable/c/c5381ae1cd1481cc431c2bd79460472c6f1d3ce3
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
Unknown CVE-2026-99212 net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure 2d
Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-98953 is "devlink: fix devlink_rel reference leak when notify work is pending", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.