CVE-2026-23014 (GCVE-0-2026-23014)
Vulnerability from cvelistv5
Published
2026-01-28 14:24
Modified
2026-08-05 12:20
Severity ?
7.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: perf: Ensure swevent hrtimer is properly destroyed With the change to hrtimer_try_to_cancel() in perf_swevent_cancel_hrtimer() it appears possible for the hrtimer to still be active by the time the event gets freed. Make sure the event does a full hrtimer_cancel() on the free path by installing a perf_event::destroy handler.
References
Impacted products
Vendor Product Version
Linux Linux Version: eb3182ef0405ff2f6668fd3e5ff9883f60ce8801
Version: eb3182ef0405ff2f6668fd3e5ff9883f60ce8801
Version: 6b8c512811644cf2f5eaf6f44e928683c54127f0
Version: 6.17.8   ≤
Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/events/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "deee9dfb111ab00f9dfd46c0c7e36656b80f5235",
              "status": "affected",
              "version": "eb3182ef0405ff2f6668fd3e5ff9883f60ce8801",
              "versionType": "git"
            },
            {
              "lessThan": "ff5860f5088e9076ebcccf05a6ca709d5935cfa9",
              "status": "affected",
              "version": "eb3182ef0405ff2f6668fd3e5ff9883f60ce8801",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "6b8c512811644cf2f5eaf6f44e928683c54127f0",
              "versionType": "git"
            },
            {
              "lessThan": "6.18",
              "status": "affected",
              "version": "6.17.8",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/events/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.18"
            },
            {
              "lessThan": "6.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.19",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.6",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "6.17.8",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nperf: Ensure swevent hrtimer is properly destroyed\n\nWith the change to hrtimer_try_to_cancel() in\nperf_swevent_cancel_hrtimer() it appears possible for the hrtimer to\nstill be active by the time the event gets freed.\n\nMake sure the event does a full hrtimer_cancel() on the free path by\ninstalling a perf_event::destroy handler."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerable code is reached through the local perf_event_open(2) syscall by creating a software cpu-clock or task-clock sampling event. There is no network, adjacent, or physical attack path.\nAC:L - The attacker controls event creation, timer activation, and fd close/release, and can repeat the sequence to hit the hrtimer lifetime race. No unusual external condition beyond normal perf availability is required.\nPR:L - A basic local user can create a per-task hrtimer-backed perf event for itself, for example with exclude_kernel=1, without needing CPU-wide or kernel-profiling privileges. More privileged modes exist, but they are not required for this vulnerable path.\nUI:N - Exploitation does not require any victim action after the attacker runs local code. The attacker can open and close the perf event directly.\nS:U - The impact remains within the kernel security authority of the same system. This is a standard local kernel memory corruption/privilege escalation scenario, not a VM escape or cross-scope boundary violation.\nC:H - The bug leaves an hrtimer callback referencing a freed perf_event object, creating a use-after-free condition. Under conservative kernel UAF scoring, this can plausibly be leveraged for kernel memory disclosure.\nI:H - The dangling callback dereferences the freed object and can reach function-pointer-bearing perf_event state such as PMU and overflow handling paths. Treating the UAF conservatively, this is plausibly exploitable for kernel control-flow or arbitrary write effects.\nA:H - Even without full exploitation, the stale hrtimer callback can dereference freed or reused kernel memory and crash or panic the system. The availability impact is therefore high."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:20:09.884Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/deee9dfb111ab00f9dfd46c0c7e36656b80f5235"
        },
        {
          "url": "https://git.kernel.org/stable/c/ff5860f5088e9076ebcccf05a6ca709d5935cfa9"
        }
      ],
      "title": "perf: Ensure swevent hrtimer is properly destroyed",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-23014",
    "datePublished": "2026-01-28T14:24:44.189Z",
    "dateReserved": "2026-01-13T15:37:45.940Z",
    "dateUpdated": "2026-08-05T12:20:09.884Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.