BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-64300High confidence

perf/aux: Fix page UAF in map_range()

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 17 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

17 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 13 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fde-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidia-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracle-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-64300 · CSAF 2.0 · revision 8 · interimSUSE Product Security TeamCVE-2026-64300
31 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1
  • kernel-default as component of SUSE Linux Enterprise Server 16.0
  • kernel-devel as component of SUSE Linux Enterprise Server 16.0
  • kernel-macros as component of SUSE Linux Enterprise Server 16.0
  • kernel-source as component of SUSE Linux Enterprise Server 16.0
  • kernel-source-vanilla as component of SUSE Linux Enterprise Server 16.0
  • kernel-default as component of SUSE Linux Enterprise Server 16.1
  • kernel-devel as component of SUSE Linux Enterprise Server 16.1
  • kernel-macros as component of SUSE Linux Enterprise Server 16.1
Summary
In the Linux kernel, the following vulnerability has been resolved: perf/aux: Fix page UAF in map_range() map_range() reads rb->aux_pages[], rb->aux_nr_pages and rb->aux_pgoff via perf_mmap_to_page() while holding only event->mmap_mutex. Those fields are serialized by rb->aux_mutex, and mmap_mutex is per event. Thus, two events sharing one rb via PERF_EVENT_IOC_SET_OUTPUT can race rb_alloc_aux() with map_range(), leading to a page-UAF scenario as follows: CPU 0 CPU 1 ===== ===== rb_alloc_aux() map_range() [1]: allocate rb->aux_pages[0] [2]: rb->aux_nr_pages++ [3]: perf_mmap_to_page() returns rb->aux_pages[0] [4]: map it as VM_PFNMAP [5]: rb->aux_pgoff = 1 munmap the page [6]: free rb->aux_pages[0] Pages mapped as VM_PFNMAP have no refcount protection, so CPU 1 holds a mapping to a freed physical frame. Fix this by taking rb->aux_mutex across the page walk in map_range().
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64300 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: perf/aux: Fix page UAF in map_range()
309 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • kernel-64k-debug-debuginfo-0:6.12.0-211.47.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-debug-devel-0:6.12.0-211.47.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-debug-devel-matched-0:6.12.0-211.47.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-debuginfo-0:6.12.0-211.47.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-devel-0:6.12.0-211.47.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-devel-matched-0:6.12.0-211.47.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.47.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.47.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.47.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.47.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-devel-0:6.12.0-211.47.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-devel-0:6.12.0-211.47.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
Summary
A flaw was found in the Linux kernel's `perf/aux` subsystem. A use-after-free (UAF) vulnerability exists in the `map_range()` function due to a race condition. This can occur when two performance events share a ring buffer, allowing a local attacker to map a memory page that has already been freed. Exploiting this flaw could lead to arbitrary code execution or privilege escalation.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-49012

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: perf/aux: Fix page UAF in map_range() map_range() reads rb->aux_pages[], rb->aux_nr_pages and rb->aux_pgoff via perf_mmap_to_page() while holding only event->mmap_mutex. Those fields are serialized by rb->aux_mutex, and mmap_mutex is per event. Thus, two events sharing one rb via PERF_EVENT_IOC_SET_OUTPUT can race rb_alloc_aux() with map_range(), leading to a page-UAF scenario as follows: CPU 0 CPU 1 ===== ===== rb_alloc_aux() map_range() [1]: allocate rb->aux_pages[0] [2]: rb->aux_nr_pages++ [3]: perf_mmap_to_page() returns rb->aux_pages[0] [4]: map it as VM_PFNMAP [5]: rb->aux_pgoff = 1 munmap the page [6]: free rb->aux_pages[0] Pages mapped as VM_PFNMAP have no refcount protection, so CPU 1 holds a mapping to a freed physical frame. Fix this by taking rb->aux_mutex across the page walk in map_range().

What

In the Linux kernel, the following vulnerability has been resolved: perf/aux: Fix page UAF in map_range() map_range() reads rb->aux_pages[], rb->aux_nr_pages and rb->aux_pgoff via perf_mmap_to_page() while holding only event->mmap_mutex. Those fields are serialized by rb->aux_mutex, and mmap_mutex is per event. Thus, two events sharing one rb via PERF_EVENT_IOC_SET_OUTPUT can race rb_alloc_aux() with map_range(), leading to a page-UAF scenario as follows: CPU 0 CPU 1 ===== ===== rb_alloc_aux() map_range() [1]: allocate rb->aux_pages[0] [2]: rb->aux_nr_pages++ [3]: perf_mmap_to_page() returns rb->aux_pages[0] [4]: map it as VM_PFNMAP [5]: rb->aux_pgoff = 1 munmap the page [6]: free rb->aux_pages[0] Pages mapped as VM_PFNMAP have no refcount protection, so CPU 1 holds a mapping to a freed physical frame. Fix this by taking rb->aux_mutex across the page walk in map_range().

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: perf/aux: Fix page UAF in map_range() map_range() reads rb->aux_pages[], rb->aux_nr_pages and rb->aux_pgoff via perf_mmap_to_page() while holding only event->mmap_mutex. Those fields are serialized by rb->aux_mutex, and mmap_mutex is per event. Thus, two events sharing one rb via PERF_EVENT_IOC_SET_OUTPUT can race rb_alloc_aux() with map_range(), leading to a page-UAF scenario as follows: CPU 0 CPU 1 ===== ===== rb_alloc_aux() map_range() [1]: allocate rb->aux_pages[0] [2]: rb->aux_nr_pages++ [3]: perf_mmap_to_page() returns rb->aux_pages[0] [4]: map it as VM_PFNMAP [5]: rb->aux_pgoff = 1 munmap the page [6]: free rb->aux_pages[0] Pages mapped as VM_PFNMAP have no refcount protection, so CPU 1 holds a mapping to a freed physical frame. Fix this by taking rb->aux_mutex across the page walk in map_range().

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-416
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2527Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260729Security Bulletin 29 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Jul 2026, published on 29 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64291 Référence CVE CVE-2026-64292 https://www.cve.org/CVERecord?id=CVE-2026-64292 Référence CVE CVE-2026-64293 https://www.cve.org/CVERecord?id=CVE-2026-64293 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64295 https://www.cve.org/CVERecord?id=CVE-2026-64295 Référence CVE CVE-2026-64296 https://www.cve.org/CVERecord?id=CVE-2026-64296 Référence CVE CVE-2026-64297 https://www.cve.org/CVERecord?id=CVE-2026-64297 Référence CVE CVE-2026-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64299 https://www.cve.org/CVERecord?id=CVE-2026-64299 Référence CVE CVE-2026-64300 https://www.cve.org/CVERecord?id=CVE-2026-64300 Référence CVE CVE-2026-64301 https://www.cve.org/CVERecord?id=CVE-2026-64301 Référence CVE CVE-2026-64302 https://www.cve.org/CVERecord?id=CVE-2026-64302 Référence CVE CVE-2026-64303 https://www.cve.org/CVERecord?id=CVE-2026-64303 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64305 https://www.cve.org/CVERecord?id=CVE-2026-64305 Référence CVE CVE-2026-64306 https://www.cve.org/CVERecord?id=CVE-2026-64306 Référence CVE CVE-2026-64307 https://www.cve.org/CVERecord?id=CVE-2026-64307 Référence CVE CVE-2026-64308 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-64277 Référence CVE CVE-2026-64278 https://www.cve.org/CVERecord?id=CVE-2026-64278 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64283 https://www.cve.org/CVERecord?id=CVE-2026-64283 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64296 https://www.cve.org/CVERecord?id=CVE-2026-64296 Référence CVE CVE-2026-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64300 https://www.cve.org/CVERecord?id=CVE-2026-64300 Référence CVE CVE-2026-64301 https://www.cve.org/CVERecord?id=CVE-2026-64301 Référence CVE CVE-2026-64303 https://www.cve.org/CVERecord?id=CVE-2026-64303 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64305 https://www.cve.org/CVERecord?id=CVE-2026-64305 Référence CVE CVE-2026-64306 https://www.cve.org/CVERecord?id=CVE-2026-64306 Référence CVE CVE-2026-64307 https://www.cve.org/CVERecord?id=CVE-2026-64307 Référence CVE CVE-2026-64308 https://www.cve.org/CVERecord?id=CVE-2026-64308 Référence CVE CVE-2026-64309 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64291 Référence CVE CVE-2026-64292 https://www.cve.org/CVERecord?id=CVE-2026-64292 Référence CVE CVE-2026-64293 https://www.cve.org/CVERecord?id=CVE-2026-64293 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64295 https://www.cve.org/CVERecord?id=CVE-2026-64295 Référence CVE CVE-2026-64296 https://www.cve.org/CVERecord?id=CVE-2026-64296 Référence CVE CVE-2026-64297 https://www.cve.org/CVERecord?id=CVE-2026-64297 Référence CVE CVE-2026-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64299 https://www.cve.org/CVERecord?id=CVE-2026-64299 Référence CVE CVE-2026-64300 https://www.cve.org/CVERecord?id=CVE-2026-64300 Référence CVE CVE-2026-64301 https://www.cve.org/CVERecord?id=CVE-2026-64301 Référence CVE CVE-2026-64302 https://www.cve.org/CVERecord?id=CVE-2026-64302 Référence CVE CVE-2026-64303 https://www.cve.org/CVERecord?id=CVE-2026-64303 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64305 https://www.cve.org/CVERecord?id=CVE-2026-64305 Référence CVE CVE-2026-64306 https://www.cve.org/CVERecord?id=CVE-2026-64306 Référence CVE CVE-2026-64307 https://www.cve.org/CVERecord?id=CVE-2026-64307 Référence CVE CVE-2026-64308 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64291 Référence CVE CVE-2026-64292 https://www.cve.org/CVERecord?id=CVE-2026-64292 Référence CVE CVE-2026-64293 https://www.cve.org/CVERecord?id=CVE-2026-64293 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64295 https://www.cve.org/CVERecord?id=CVE-2026-64295 Référence CVE CVE-2026-64296 https://www.cve.org/CVERecord?id=CVE-2026-64296 Référence CVE CVE-2026-64297 https://www.cve.org/CVERecord?id=CVE-2026-64297 Référence CVE CVE-2026-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64299 https://www.cve.org/CVERecord?id=CVE-2026-64299 Référence CVE CVE-2026-64300 https://www.cve.org/CVERecord?id=CVE-2026-64300 Référence CVE CVE-2026-64301 https://www.cve.org/CVERecord?id=CVE-2026-64301 Référence CVE CVE-2026-64302 https://www.cve.org/CVERecord?id=CVE-2026-64302 Référence CVE CVE-2026-64303 https://www.cve.org/CVERecord?id=CVE-2026-64303 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64305 https://www.cve.org/CVERecord?id=CVE-2026-64305 Référence CVE CVE-2026-64306 https://www.cve.org/CVERecord?id=CVE-2026-64306 Référence CVE CVE-2026-64307 https://www.cve.org/CVERecord?id=CVE-2026-64307 Référence CVE CVE-2026-64308 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64291 Référence CVE CVE-2026-64292 https://www.cve.org/CVERecord?id=CVE-2026-64292 Référence CVE CVE-2026-64293 https://www.cve.org/CVERecord?id=CVE-2026-64293 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64295 https://www.cve.org/CVERecord?id=CVE-2026-64295 Référence CVE CVE-2026-64296 https://www.cve.org/CVERecord?id=CVE-2026-64296 Référence CVE CVE-2026-64297 https://www.cve.org/CVERecord?id=CVE-2026-64297 Référence CVE CVE-2026-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64299 https://www.cve.org/CVERecord?id=CVE-2026-64299 Référence CVE CVE-2026-64300 https://www.cve.org/CVERecord?id=CVE-2026-64300 Référence CVE CVE-2026-64301 https://www.cve.org/CVERecord?id=CVE-2026-64301 Référence CVE CVE-2026-64302 https://www.cve.org/CVERecord?id=CVE-2026-64302 Référence CVE CVE-2026-64303 https://www.cve.org/CVERecord?id=CVE-2026-64303 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64305 https://www.cve.org/CVERecord?id=CVE-2026-64305 Référence CVE CVE-2026-64306 https://www.cve.org/CVERecord?id=CVE-2026-64306 Référence CVE CVE-2026-64307 https://www.cve.org/CVERecord?id=CVE-2026-64307 Référence CVE CVE-2026-64308 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1028Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-45991 Référence CVE CVE-2026-46054 https://www.cve.org/CVERecord?id=CVE-2026-46054 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-53009 https://www.cve.org/CVERecord?id=CVE-2026-53009 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53202 https://www.cve.org/CVERecord?id=CVE-2026-53202 Référence CVE CVE-2026-53264 https://www.cve.org/CVERecord?id=CVE-2026-53264 Référence CVE CVE-2026-63887 https://www.cve.org/CVERecord?id=CVE-2026-63887 Référence CVE CVE-2026-64300 https://www.cve.org/CVERecord?id=CVE-2026-64300 Référence CVE CVE-2026-64368 https://www.cve.org/CVERecord?id=CVE-2026-64368 Référence CVE CVE-2026-64496 https://www.cve.org/CVERecord?id=CVE-2026-64496 Référence CVE CVE-2026-64531 https://www.cve.org/CVERecord?id=CVE-2026-64531 Gestion détaillée du document le 14 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des sy

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-031801LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました：perf/auxのmap_range()におけるページUAFの修正です。map_range()は、perf_mmap_to_page()を介してrb-＞aux_pages[]、rb-＞aux_nr_pages、およびrb-＞aux_pgoffを読み取りますが、このとき保持しているのはevent-＞mmap_mutexのみです。これらのフィールドはrb-＞aux_mutexによって直列化されていますが、mmap_mutexはイベントごとのロックです。そのため、PERF_EVENT_IOC_SET_OUTPUTを介して1つのrbを共有する2つのイベントが、rb_alloc_aux()とmap_range()で競合し、以下のようなページUAF（Use-After-Free）のシナリオが発生します： CPU 0 CPU 1 ===== ===== rb_alloc_aux() map_range() [1]: rb-＞aux_pages[0]を割り当て [2]: rb-＞aux_nr_pages++ [3]: perf_mmap_to_page()がrb-＞aux_pages[0]を返す [4]: それをVM_PFNMAPとしてマッピング [5]: rb-＞aux_pgoff = 1 ページをmunmap [6]: rb-＞aux_pages[0]を解放VM_PFNMAPとしてマッピングされたページはリファレンスカウントによる保護がないため、CPU 1は解放された物理フレームへのマッピングを保持したままとなります。これを修正するために、map_range()内のページウォーク全体にわたりrb-＞aux_mutexを取得するように変更しました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.14, 6.18.39 ≤ 6.18.*, 7.1.4 ≤ 7.1.*, 7.2 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 25 Jul 2026 · Last source change 17 Aug 2026, 04:52 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-49012
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added patch: git.kernel.org/0cff05bd2186020f8706233e261016d149cc24db; added patch: git.kernel.org/5948aaf64f81f217a25dcc2bf6c0779bca19566c; 1 further additions.
    Before
    remediation: git.kernel.org/c8b7e113f7b61eef2f017e6329c27c2331058c5a
    After
    patch: git.kernel.org/0cff05bd2186020f8706233e261016d149cc24db · patch: git.kernel.org/5948aaf64f81f217a25dcc2bf6c0779bca19566c · patch: git.kernel.org/c8b7e113f7b61eef2f017e6329c27c2331058c5a · 1 more references
    git.kernel.org ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    b709eb872e19a19607bbb6d2975bc264d59735cf < c8b7e113f7b61eef2f017e6329c27c2331058c5a; b709eb872e19a19607bbb6d2975bc264d59735cf < 0cff05bd2186020f8706233e261016d149cc24db; b709eb872e19a19607bbb6d2975bc264d59735cf < 5948aaf64f81f217a25dcc2bf6c0779bca19566c; 6.14 · Fixed: < 6.14; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2-rc3 ≤ *
    After
    b709eb872e19a19607bbb6d2975bc264d59735cf < c8b7e113f7b61eef2f017e6329c27c2331058c5a; b709eb872e19a19607bbb6d2975bc264d59735cf < 0cff05bd2186020f8706233e261016d149cc24db; b709eb872e19a19607bbb6d2975bc264d59735cf < 5948aaf64f81f217a25dcc2bf6c0779bca19566c; 6.14 · Fixed: < 6.14; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-49012↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-64300 · cve.blacktree.nl