LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23014: perf: Ensure swevent hrtimer is properly destroyed

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-23014 is a Linux kernel flaw in the perf subsystem. A local low-privileged user could potentially trigger serious memory-safety impact, reflected by high confidentiality, integrity, and availability CVSS impacts. It is not remotely exploitable based on the supplied vector, and no active exploitation is cited.

Executive priority

Prioritize normal emergency patch handling for exposed Linux fleets, especially shared or multi-tenant systems. This is high severity but currently source-supported as local-only and not known exploited.

Technical view

The issue involves perf software event hrtimer cleanup. The source states hrtimer_try_to_cancel() could leave the timer active when the event is freed. The fix adds a perf_event destroy handler that performs full hrtimer_cancel() during object teardown.

Likely exposure

Exposure is most relevant on Linux systems running affected kernel builds around the supplied 6.18 and 6.19 entries. Systems with untrusted local users, shared shells, build hosts, or container workloads deserve closer review. The affected-version data is incomplete, so distribution mapping is required.

Exploitation context

The CVSS vector is local, low complexity, low privileges, no user interaction, with high CIA impact. The source bundle does not cite public exploitation, exploit availability, or CISA KEV listing. Treat exploitation status as unconfirmed.

Researcher notes

The supplied record lacks CWE, detailed version-range semantics, and exploit evidence. Analysis should focus on commit ancestry, distro backports, and perf event lifecycle behavior around swevent hrtimer destruction.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Check distribution vendor advisories for backported kernel package status.
  • Prioritize multi-user, developer, container, and shared hosting systems.
  • Restrict unnecessary local account access where practical until patched.
  • Track kernel versions that map to the supplied affected range.

Validation and detection

  • Inventory Linux kernel versions across servers, workstations, and images.
  • Confirm whether deployed kernels include the referenced stable commits.
  • Review vendor changelogs for CVE-2026-23014 backports.
  • Identify systems exposing local perf access to untrusted users.
  • Retest after patching by confirming the updated kernel package is running.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23014 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-23014Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxeb3182ef0405ff2f6668fd3e5ff9883f60ce8801, eb3182ef0405ff2f6668fd3e5ff9883f60ce8801, 6b8c512811644cf2f5eaf6f44e928683c54127f0, 6.17.8unaffected
LinuxLinux6.18, 0, 6.18.6, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.