{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Set the trace clock before registering the histogram trigger  hist_register_trigger() puts the trigger on the global named_triggers list in cmd_ops-\u003einit(), and only then sets the trace clock:  \tif (data-\u003ecmd_ops-\u003einit) { \t\tret = data-\u003ecmd_ops-\u003einit(data); \t\tif (ret \u003c 0) \t\t\tgoto out; \t}  \tif (hist_data-\u003eenable_timestamps) { \t\tret = tracing_set_clock(file-\u003etr, hist_data-\u003eattrs-\u003eclock); \t\tif (ret) { \t\t\thist_err(tr, HIST_ERR_SET_CLOCK_FAIL, errpos(clock)); \t\t\tgoto out; \t\t}  The clock string is not checked anywhere before that call, so a named trigger using common_timestamp with an unknown clock fails after it has already become findable. event_hist_trigger_parse() then frees it without taking it off the list, and the next lookup by name reads the freed object:   ~# cd /sys/kernel/tracing/events/sched/sched_switch  ~# echo 'hist:name=foo:keys=common_pid:ts=common_timestamp:clock=bogus' \u003e trigger  bash: echo: write error: Invalid argument  ~# echo 'hist:name=foo:keys=common_pid' \u003e trigger    BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0   Read of size 8 at addr ffff88800915d760 by task init/1    find_named_trigger+0xac/0xc0    hist_register_trigger+0xc1/0x900    event_hist_trigger_parse+0x3146/0x6af0    event_trigger_write+0xce/0x160   Freed by task 63:    kfree+0x154/0x420    trigger_kthread_fn+0xfd/0x160  Set the clock before the trigger is registered, so that nothing which can fail runs after it is published, the way commit 6f86bdeab633 (\"tracing: Fix bad hist from corrupting named_triggers list\") moved the registration below the rest of the setup.  tracing_set_filter_buffering() is reference counted, so the init failure path has to drop the reference that the clock block now takes first.",
  "id": "DEBIAN-CVE-2026-97935",
  "modified": "2026-09-26T04:47:34.031444142Z",
  "published": "2026-09-25T11:17:20.850Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-97935"
    }
  ],
  "upstream": [
    "CVE-2026-97935"
  ]
}