{
  "id": "CVE-2026-98076",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-98076",
  "published_at": "2026-09-25T10:24:15.085Z",
  "title": "tracing/probes: Fix use-after-free on field name/type of events with multiple probes",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7.8,
    "source": "nvd",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\ntracing/probes: Fix use-after-free on field name/type of events with multiple probes\n\nThe fields of a probe-based dynamic event (kprobe, uprobe, eprobe and\nfprobe events) are created in traceprobe_define_arg_fields() by handing\nthe probe_arg name/type strings to trace_define_field(), which only\nstores the pointers without copying. Those strings are owned by the\ntrace_probe and are freed when that probe is removed.\n\nAn event can have several probes attached. The field list is defined\nonly once, by the first probe that registers the event, but it is kept\nalive by any surviving sibling probe. Deleting just that first probe by\nsymbol -\n\n  # primary A: fields are defined from A's args\n  echo 'p:kprobes/ev vfs_read  a1=$arg1' \u003e  kprobe_events\n  # append B: shares A's event call\n  echo 'p:kprobes/ev vfs_write a1=$arg1' \u003e\u003e kprobe_events\n  # delete only A (matched by symbol), B survives\n  echo '-:kprobes/ev vfs_read'           \u003e\u003e kprobe_events\n\nfrees A's args (trace_probe_cleanup() -\u003e traceprobe_free_probe_arg()),\nbut trace_probe_unlink() keeps the trace_probe_event because the probe\nlist is not empty. The event call stays registered via B while its\nfields now reference freed memory. Any field lookup then reads it, e.g.\n\n  echo 'a1 == 1' \u003e events/kprobes/ev/filter\n\n  BUG: KASAN: slab-use-after-free in strcmp+0xa7/0xb0\n  Call Trace:\n   strcmp\n   trace_find_event_field\n   parse_pred\n   process_preds\n   create_filter\n   apply_event_filter\n   event_filter_write\n\nfield-\u003ename references parg-\u003ename (kstrdup'd, freed with the probe) and,\nfor array arguments, field-\u003etype references parg-\u003efmt (kmalloc'd, freed\nwith the probe) - the scalar type otherwise points at the static\nfmttype rodata, which is safe.\n\nHave traceprobe_define_arg_fields() duplicate the name and type strings\nand anchor the copies on the trace_probe_event, which embeds the event\ncall and outlives every individual probe; trace_probe_event_free()\nreleases them.\n\nThe reproducer above triggers reliably; the field lookup and the delete\nboth run under event_mutex, so this is a dangling reference after\nremoval rather than a race.\n\nThe issue was found by the autokbug dynamic kernel fuzzer at Tencent\nYunding Lab.",
  "cwe": "CWE-416",
  "cpes": [
    "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
    "cpe:2.3:o:linux:linux_kernel:7.3:rc1:*:*:*:*:*:*"
  ],
  "cvss_by_source": {
    "nvd": 7.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= ca89bc071d5e4e981dcc52e0ca90f4500d332e42, \u003c 38305e1b8b1ec27eef8f2d4e461e3b6c8624d494",
          "\u003e= ca89bc071d5e4e981dcc52e0ca90f4500d332e42, \u003c 6d6118c17bc791594cbfd9cc4936ee21073b894a",
          "\u003e= ca89bc071d5e4e981dcc52e0ca90f4500d332e42, \u003c a2510fcaad92b09b34574c97e8356234c6a84a9a",
          "\u003e= ca89bc071d5e4e981dcc52e0ca90f4500d332e42, \u003c 9379e193826f23876daccb3351fab89c87084ba3",
          "\u003e= ca89bc071d5e4e981dcc52e0ca90f4500d332e42, \u003c 68ae584169c7a41fc9bc4677c1d368983cf44b21",
          "\u003e= ca89bc071d5e4e981dcc52e0ca90f4500d332e42, \u003c 411c9080a776577664531b4f7d3ee53b7a747ba8",
          "\u003e= ca89bc071d5e4e981dcc52e0ca90f4500d332e42, \u003c 178ff2e011e21fbebdf57f5d58a408fe59136d82",
          "\u003e= ca89bc071d5e4e981dcc52e0ca90f4500d332e42, \u003c 86b7a239ec6b14a7544200ede85474c6f5526049"
        ],
        "fixed_in": [
          "38305e1b8b1ec27eef8f2d4e461e3b6c8624d494",
          "6d6118c17bc791594cbfd9cc4936ee21073b894a",
          "a2510fcaad92b09b34574c97e8356234c6a84a9a",
          "9379e193826f23876daccb3351fab89c87084ba3",
          "68ae584169c7a41fc9bc4677c1d368983cf44b21",
          "411c9080a776577664531b4f7d3ee53b7a747ba8",
          "178ff2e011e21fbebdf57f5d58a408fe59136d82",
          "86b7a239ec6b14a7544200ede85474c6f5526049"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "5.4"
        ],
        "fixed_in": [
          "0",
          "5.10.271",
          "5.15.222",
          "6.1.189",
          "6.6.158",
          "6.12.111",
          "6.18.53",
          "7.2.7",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 38305e1b8b1ec27eef8f2d4e461e3b6c8624d494 or 6d6118c17bc791594cbfd9cc4936ee21073b894a or a2510fcaad92b09b34574c97e8356234c6a84a9a or 9379e193826f23876daccb3351fab89c87084ba3 or 68ae584169c7a41fc9bc4677c1d368983cf44b21 or 411c9080a776577664531b4f7d3ee53b7a747ba8 or 178ff2e011e21fbebdf57f5d58a408fe59136d82 or 86b7a239ec6b14a7544200ede85474c6f5526049 or later.",
      "Upgrade Linux to 0 or 5.10.271 or 5.15.222 or 6.1.189 or 6.6.158 or 6.12.111 or 6.18.53 or 7.2.7 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
