{
  "cveId": "CVE-2026-46008",
  "url": "https://patchblox.com/security/cve/CVE-2026-46008",
  "summary": "CVE-2026-46008 is fixed in linux on 1 platform by DEBIAN-CVE-2026-46008 (version 7.0.4-1), released May 27, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  mm/damon/core: fix damos_walk() vs kdamond_fn()...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  mm/damon/core: fix damos_walk() vs kdamond_fn() exit race  When kdamond_fn() main loop is finished, the function cancels remaining damos_walk() request and unset the damon_ctx-\u003Ekdamond so that API callers and API functions themselves can show the context is terminated.  damos_walk() adds the caller\u0027s request to the queue first.  After that, it shows if the kdamond of the damon_ctx is still running (damon_ctx-\u003Ekdamond is set).  Only if the kdamond is running, damos_walk() starts waiting for the kdamond\u0027s handling of the newly added request.  The damos_walk() requests registration and damon_ctx-\u003Ekdamond unset are protected by different mutexes, though.  Hence, damos_walk() could race with damon_ctx-\u003Ekdamond unset, and result in deadlocks.  For example, let\u0027s suppose kdamond successfully finished the damow_walk() request cancelling.  Right after that, damos_walk() is called for the context.  It registers the new request, and shows the context is still running, because damon_ctx-\u003Ekdamond unset is not yet done.  Hence the damos_walk() caller starts waiting for the handling of the request.  However, the kdamond is already on the termination steps, so it never handles the new request.  As a result, the damos_walk() caller thread infinitely waits.  Fix this by introducing another damon_ctx field, namely walk_control_obsolete.  It is protected by the damon_ctx-\u003Ewalk_control_lock, which protects damos_walk() request registration.  Initialize (unset) it in kdamond_fn() before letting damon_start() returns and set it just before the cancelling of the remaining damos_walk() request is executed.  damos_walk() reads the obsolete field under the lock and avoids adding a new request.  After this change, only requests that are guaranteed to be handled or cancelled are registered.  Hence the after-registration DAMON context termination check is no longer needed.  Remove it together.  The issue is found by sashiko [1].",
  "published": "2026-05-27T14:17:18Z",
  "severity": "medium",
  "cvss": 4.7,
  "cvssVector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.0009,
  "epssPercentile": 0.00428,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.0.4-1",
      "fix": "DEBIAN-CVE-2026-46008",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-46008",
      "released": "2026-05-27T17:38:13Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T06:59:42Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}