dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53114

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.18.33 / 7.0.10 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: perf/amd/ibs: Avoid calling perf_allow_kernel() from the IBS NMI handler Calling perf_allow_kernel() from the NMI context is unsafe and could be fatal. Capture the permission at event-initialization time by storing it in event->hw.flags, and have the NMI handler rely on that cached flag instead of making the call directly.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The AMD IBS (Instruction Based Sampling) perf subsystem in the Linux kernel incorrectly calls perf_allow_kernel() from within the NMI handler context. NMI handlers run with interrupts disabled in atomic context, making function calls that may acquire locks or sleep unsafe and potentially fatal. The vulnerability is resolved by caching the permission check result during event initialization in event->hw.flags, allowing the NMI handler to safely read the pre-computed flag.

MitigationUpdate the Linux kernel to the version containing the fix that caches permission checks at event initialization rather than calling perf_allow_kernel() from NMI context. For systems unable to update immediately, avoid enabling perf IBS events in kernel mode as a workaround.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.14.1, < 6.18.33>= 6.19, < 7.0.10= 6.14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version against affected ranges
    Run 'uname -r' or 'cat /proc/version' to get the running kernel version. Compare against: 6.14, >= 6.14.1 and < 6.18.33, >= 6.19 and < 7.0.10
    Affected if The installed kernel version falls within any of the affected ranges listed above
  2. Confirm AMD hardware with IBS support
    Check CPU vendor: 'grep -m1 vendor_id /proc/cpuinfo' should show 'AuthenticAMD'. For IBS specifically, check 'cpuid | grep -i ibs' or check CPU model details
    Affected if System is running on AMD processor that supports Instruction Based Sampling (IBS) feature
  3. Verify AMD IBS driver is enabled
    Check kernel config: 'grep -i "ibs" /boot/config-$(uname -r)' or check if module 'kvm-amd' with IBS support is loaded via 'lsmod | grep -i amd'. Also check /sys/devices/system/cpu/cpu0/ibs/ for IBS sysfs nodes
    Affected if The AMD IBS driver or KVM with IBS support is loaded/enabled in the running kernel
  4. Check for IBS performance event availability
    List available perf events: 'perf list | grep -i ibs' or check /sys/bus/event_source/devices/ for ibs* entries
    Affected if IBS performance monitoring events are available to userspace, indicating the driver is active

System is affected if running a vulnerable kernel version (6.14, 6.14.1-6.18.32, or 6.19-7.0.9) on AMD hardware with the IBS driver enabled and accessible to userspace.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.18.33 / 7.0.10 or later
Fixed in 6.18.337.0.10
Vendor patch git.kernel.org →
Interim mitigation

Update the Linux kernel to the version containing the fix that caches permission checks at event initialization rather than calling perf_allow_kernel() from NMI context. For systems unable to update immediately, avoid enabling perf IBS events in kernel mode as a workaround.

Recommended fix High confidence

6.18.33, 7.0.10, or later stable kernel versions

  1. Apply the kernel patch that moves perf_allow_kernel() call from the IBS NMI handler to event initialization time
  2. Ensure the permission is cached in event->hw.flags during event initialization
  3. Rebuild and deploy the patched kernel

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53114 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data