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

vfio/pci: Check BAR resources before exporting a DMABUF

Linux · Linux

8.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 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.17% 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.0.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-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.

1 current
CVE-2026-64042 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: vfio/pci: Check BAR resources before exporting a DMABUF
309 fixed

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

  • kernel-64k-debug-debuginfo-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-debug-devel-0:6.12.0-211.53.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.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-debuginfo-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-devel-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-devel-matched-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-devel-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-devel-0:6.12.0-211.53.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 vfio/pci subsystem. This vulnerability occurs because the Direct Memory Access Buffer (DMABUF) export mechanism does not adequately verify if Base Address Register (BAR) resources are properly reserved before allowing access. A local attacker could exploit this by exporting a DMABUF, potentially gaining unauthorized access to unreserved system resources. This could lead to information disclosure or other unintended system behavior.
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-45615

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: vfio/pci: Check BAR resources before exporting a DMABUF A DMABUF exports access to BAR resources and, although they are requested at startup time, we need to ensure they really were reserved before exporting. Otherwise, it's possible to access unreserved resources through the export. Add a check to the DMABUF-creation path.

What

In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Check BAR resources before exporting a DMABUF A DMABUF exports access to BAR resources and, although they are requested at startup time, we need to ensure they really were reserved before exporting. Otherwise, it's possible to access unreserved resources through the export. Add a check to the DMABUF-creation path.

Why

The application reaches a protected operation without first confirming that the requester is authorised.

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: vfio/pci: Check BAR resources before exporting a DMABUF A DMABUF exports access to BAR resources and, although they are requested at startup time, we need to ensure they really were reserved before exporting. Otherwise, it's possible to access unreserved resources through the export. Add a check to the DMABUF-creation path.

Why

The application reaches a protected operation without first confirming that the requester is authorised.

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 → Missing Authorization → 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
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-862 ↗

CWE-862: Missing Authorization. The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

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:C/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.SChangedScope: The attack can affect a component governed by a different security 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-862
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

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

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 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-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64035 https://www.cve.org/CVERecord?id=CVE-2026-64035 Référence CVE CVE-2026-64036 https://www.cve.org/CVERecord?id=CVE-2026-64036 Référence CVE CVE-2026-64037 https://www.cve.org/CVERecord?id=CVE-2026-64037 Référence CVE CVE-2026-64038 https://www.cve.org/CVERecord?id=CVE-2026-64038 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64040 https://www.cve.org/CVERecord?id=CVE-2026-64040 Référence CVE CVE-2026-64041 https://www.cve.org/CVERecord?id=CVE-2026-64041 Référence CVE CVE-2026-64042 https://www.cve.org/CVERecord?id=CVE-2026-64042 Référence CVE CVE-2026-64043 https://www.cve.org/CVERecord?id=CVE-2026-64043 Référence CVE CVE-2026-64044 https://www.cve.org/CVERecord?id=CVE-2026-64044 Référence CVE CVE-2026-64045 https://www.cve.org/CVERecord?id=CVE-2026-64045 Référence CVE CVE-2026-64046 https://www.cve.org/CVERecord?id=CVE-2026-64046 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64049 https://www.cve.org/CVERecord?id=CVE-2026-64049 Référence CVE CVE-2026-64050 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-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64035 https://www.cve.org/CVERecord?id=CVE-2026-64035 Référence CVE CVE-2026-64036 https://www.cve.org/CVERecord?id=CVE-2026-64036 Référence CVE CVE-2026-64037 https://www.cve.org/CVERecord?id=CVE-2026-64037 Référence CVE CVE-2026-64038 https://www.cve.org/CVERecord?id=CVE-2026-64038 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64040 https://www.cve.org/CVERecord?id=CVE-2026-64040 Référence CVE CVE-2026-64041 https://www.cve.org/CVERecord?id=CVE-2026-64041 Référence CVE CVE-2026-64042 https://www.cve.org/CVERecord?id=CVE-2026-64042 Référence CVE CVE-2026-64043 https://www.cve.org/CVERecord?id=CVE-2026-64043 Référence CVE CVE-2026-64044 https://www.cve.org/CVERecord?id=CVE-2026-64044 Référence CVE CVE-2026-64045 https://www.cve.org/CVERecord?id=CVE-2026-64045 Référence CVE CVE-2026-64046 https://www.cve.org/CVERecord?id=CVE-2026-64046 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64049 https://www.cve.org/CVERecord?id=CVE-2026-64049 Référence CVE CVE-2026-64050 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-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64035 https://www.cve.org/CVERecord?id=CVE-2026-64035 Référence CVE CVE-2026-64036 https://www.cve.org/CVERecord?id=CVE-2026-64036 Référence CVE CVE-2026-64037 https://www.cve.org/CVERecord?id=CVE-2026-64037 Référence CVE CVE-2026-64038 https://www.cve.org/CVERecord?id=CVE-2026-64038 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64040 https://www.cve.org/CVERecord?id=CVE-2026-64040 Référence CVE CVE-2026-64041 https://www.cve.org/CVERecord?id=CVE-2026-64041 Référence CVE CVE-2026-64042 https://www.cve.org/CVERecord?id=CVE-2026-64042 Référence CVE CVE-2026-64043 https://www.cve.org/CVERecord?id=CVE-2026-64043 Référence CVE CVE-2026-64044 https://www.cve.org/CVERecord?id=CVE-2026-64044 Référence CVE CVE-2026-64045 https://www.cve.org/CVERecord?id=CVE-2026-64045 Référence CVE CVE-2026-64046 https://www.cve.org/CVERecord?id=CVE-2026-64046 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64049 https://www.cve.org/CVERecord?id=CVE-2026-64049 Référence CVE CVE-2026-64050 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64035 https://www.cve.org/CVERecord?id=CVE-2026-64035 Référence CVE CVE-2026-64036 https://www.cve.org/CVERecord?id=CVE-2026-64036 Référence CVE CVE-2026-64037 https://www.cve.org/CVERecord?id=CVE-2026-64037 Référence CVE CVE-2026-64038 https://www.cve.org/CVERecord?id=CVE-2026-64038 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64040 https://www.cve.org/CVERecord?id=CVE-2026-64040 Référence CVE CVE-2026-64041 https://www.cve.org/CVERecord?id=CVE-2026-64041 Référence CVE CVE-2026-64042 https://www.cve.org/CVERecord?id=CVE-2026-64042 Référence CVE CVE-2026-64043 https://www.cve.org/CVERecord?id=CVE-2026-64043 Référence CVE CVE-2026-64044 https://www.cve.org/CVERecord?id=CVE-2026-64044 Référence CVE CVE-2026-64045 https://www.cve.org/CVERecord?id=CVE-2026-64045 Référence CVE CVE-2026-64046 https://www.cve.org/CVERecord?id=CVE-2026-64046 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64049 https://www.cve.org/CVERecord?id=CVE-2026-64049 Référence CVE CVE-2026-64050 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64035 https://www.cve.org/CVERecord?id=CVE-2026-64035 Référence CVE CVE-2026-64036 https://www.cve.org/CVERecord?id=CVE-2026-64036 Référence CVE CVE-2026-64037 https://www.cve.org/CVERecord?id=CVE-2026-64037 Référence CVE CVE-2026-64038 https://www.cve.org/CVERecord?id=CVE-2026-64038 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64040 https://www.cve.org/CVERecord?id=CVE-2026-64040 Référence CVE CVE-2026-64041 https://www.cve.org/CVERecord?id=CVE-2026-64041 Référence CVE CVE-2026-64042 https://www.cve.org/CVERecord?id=CVE-2026-64042 Référence CVE CVE-2026-64043 https://www.cve.org/CVERecord?id=CVE-2026-64043 Référence CVE CVE-2026-64044 https://www.cve.org/CVERecord?id=CVE-2026-64044 Référence CVE CVE-2026-64045 https://www.cve.org/CVERecord?id=CVE-2026-64045 Référence CVE CVE-2026-64046 https://www.cve.org/CVERecord?id=CVE-2026-64046 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64049 https://www.cve.org/CVERecord?id=CVE-2026-64049 Référence CVE CVE-2026-64050 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64035 https://www.cve.org/CVERecord?id=CVE-2026-64035 Référence CVE CVE-2026-64036 https://www.cve.org/CVERecord?id=CVE-2026-64036 Référence CVE CVE-2026-64037 https://www.cve.org/CVERecord?id=CVE-2026-64037 Référence CVE CVE-2026-64038 https://www.cve.org/CVERecord?id=CVE-2026-64038 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64040 https://www.cve.org/CVERecord?id=CVE-2026-64040 Référence CVE CVE-2026-64041 https://www.cve.org/CVERecord?id=CVE-2026-64041 Référence CVE CVE-2026-64042 https://www.cve.org/CVERecord?id=CVE-2026-64042 Référence CVE CVE-2026-64043 https://www.cve.org/CVERecord?id=CVE-2026-64043 Référence CVE CVE-2026-64044 https://www.cve.org/CVERecord?id=CVE-2026-64044 Référence CVE CVE-2026-64045 https://www.cve.org/CVERecord?id=CVE-2026-64045 Référence CVE CVE-2026-64046 https://www.cve.org/CVERecord?id=CVE-2026-64046 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64049 https://www.cve.org/CVERecord?id=CVE-2026-64049 Référence CVE CVE-2026-64050 https://www.cve.org/CVERecord?id=

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
Linux: 5d74781ebc86c5fa9e9d6934024c505412de9b52 < 8443cd4497a4498c4b01058d76a92116244cb605, 5d74781ebc86c5fa9e9d6934024c505412de9b52 < 702809dabdecca807bdd50cfdcc1c980feb2ba62, 6.19
Fixed
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 19 Jul 2026 · Last source change 5 Aug 2026, 12:38 UTC · CWE-862 · Missing Authorization

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-45615
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
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/702809dabdecca807bdd50cfdcc1c980feb2ba62; added patch: git.kernel.org/8443cd4497a4498c4b01058d76a92116244cb605.
    Before
    remediation: git.kernel.org/8443cd4497a4498c4b01058d76a92116244cb605
    After
    patch: git.kernel.org/702809dabdecca807bdd50cfdcc1c980feb2ba62 · patch: git.kernel.org/8443cd4497a4498c4b01058d76a92116244cb605 · remediation: git.kernel.org/8443cd4497a4498c4b01058d76a92116244cb605
    git.kernel.org ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    5d74781ebc86c5fa9e9d6934024c505412de9b52 < 8443cd4497a4498c4b01058d76a92116244cb605; 5d74781ebc86c5fa9e9d6934024c505412de9b52 < 702809dabdecca807bdd50cfdcc1c980feb2ba62; 6.19 · Fixed: < 6.19; 7.0.11 ≤ 7.0.*; 7.1 ≤ *
    After
    Linux: 5d74781ebc86c5fa9e9d6934024c505412de9b52 < 8443cd4497a4498c4b01058d76a92116244cb605, 5d74781ebc86c5fa9e9d6934024c505412de9b52 < 702809dabdecca807bdd50cfdcc1c980feb2ba62, 6.19 · Fixed: Linux: < 6.19, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
    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-45615↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor 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-64042 · cve.blacktree.nl