FKIE_CVE-2026-98953

Vulnerability from fkie_nvd - Published: 2026-10-23 13:17 - Updated: 2026-10-23 13:17
Severity
Summary
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.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/8c7830e0120e6e1f5084212fd5b79b3092496f87
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/8de57bfec3825effb57fe4d25da98ec3b8fda4c6
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/c5381ae1cd1481cc431c2bd79460472c6f1d3ce3
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/dc2e787b5fb474241c8a6d18fdacb44adc6d571f
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/devlink/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "8c7830e0120e6e1f5084212fd5b79b3092496f87",
              "status": "affected",
              "version": "c137743bce02b18c1537d4681aa515f7b80bf0a8",
              "versionType": "git"
            },
            {
              "lessThan": "8de57bfec3825effb57fe4d25da98ec3b8fda4c6",
              "status": "affected",
              "version": "c137743bce02b18c1537d4681aa515f7b80bf0a8",
              "versionType": "git"
            },
            {
              "lessThan": "dc2e787b5fb474241c8a6d18fdacb44adc6d571f",
              "status": "affected",
              "version": "c137743bce02b18c1537d4681aa515f7b80bf0a8",
              "versionType": "git"
            },
            {
              "lessThan": "c5381ae1cd1481cc431c2bd79460472c6f1d3ce3",
              "status": "affected",
              "version": "c137743bce02b18c1537d4681aa515f7b80bf0a8",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/devlink/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.7"
            },
            {
              "lessThan": "6.7",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.113",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.57",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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": "CVE-2026-98953",
  "lastModified": "2026-10-23T13:17:16.480",
  "metrics": {},
  "published": "2026-10-23T13:17:16.480",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/8c7830e0120e6e1f5084212fd5b79b3092496f87"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/8de57bfec3825effb57fe4d25da98ec3b8fda4c6"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/c5381ae1cd1481cc431c2bd79460472c6f1d3ce3"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/dc2e787b5fb474241c8a6d18fdacb44adc6d571f"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    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.