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

RDMA/bnxt_re: zero shared page before exposing to userspace

Linux · Linux

7.1HighCVSS 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 280 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • 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: Within 30 daysRemediation target: Within 180 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 280 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.

24 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 20 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 · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.95-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.177-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.14-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.14-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, 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-awsAffected, 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-azureAffected, 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-fdeAffected, 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-nvidiaAffected, 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-gcpAffected, 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-gkeAffected, 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-gkeopAffected, 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-ibmAffected, 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-lowlatencyAffected, 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-nvidiaAffected, 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-lowlatencyAffected, 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-tegraAffected, 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-oracleAffected, 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-raspiAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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-74584 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-74584
279 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • 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
Summary
In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: zero shared page before exposing to userspace bnxt_re_alloc_ucontext() allocates uctx->shpg via __get_free_page(GFP_KERNEL). The buddy allocator does not zero pages without __GFP_ZERO, so the page contains stale kernel data from whatever object most recently freed it. The page is then mapped into userspace via vm_insert_page() under BNXT_RE_MMAP_SH_PAGE in bnxt_re_mmap(). The driver only ever writes 4 bytes (a u32 AVID) at offset BNXT_RE_AVID_OFFT (0x10) inside bnxt_re_create_ah(); the remaining 4092 bytes of the page are exposed to userspace unsanitised, leaking kernel memory contents. Any user with access to /dev/infiniband/uverbsX on a host with a bnxt_re device (typically rdma group membership) can read this data via a single mmap() at pgoff 0 after IB_USER_VERBS_CMD_GET_CONTEXT. Other shared pages in the same file already use get_zeroed_page() correctly: drivers/infiniband/hw/bnxt_re/ib_verbs.c srq->uctx_srq_page = (void *)get_zeroed_page(GFP_KERNEL); cq->uctx_cq_page = (void *)get_zeroed_page(GFP_KERNEL); uctx->shpg is the only outlier. Bring it in line with the existing convention by switching to get_zeroed_page().
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-74584 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: RDMA/bnxt_re: zero shared page before exposing to userspace
260 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's RDMA/bnxt_re component. A local attacker with access to the RDMA device could exploit this vulnerability due to a failure to zero out a shared memory page before exposing it to userspace. This could lead to information disclosure, allowing the attacker to read sensitive kernel memory contents.
Remediation
Fix deferred
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-64332

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: zero shared page before exposing to userspace bnxt_re_alloc_ucontext() allocates uctx->shpg via __get_free_page(GFP_KERNEL). The buddy allocator does not zero pages without __GFP_ZERO, so the page contains stale kernel data from whatever object most recently freed it. The page is then mapped into userspace via vm_insert_page() under BNXT_RE_MMAP_SH_PAGE in bnxt_re_mmap(). The driver only ever writes 4 bytes (a u32 AVID) at offset BNXT_RE_AVID_OFFT (0x10) inside bnxt_re_create_ah(); the remaining 4092 bytes of the page are exposed to userspace unsanitised, leaking kernel memory contents. Any user with access to /dev/infiniband/uverbsX on a host with a bnxt_re device (typically rdma group membership) can read this data via a single mmap() at pgoff 0 after IB_USER_VERBS_CMD_GET_CONTEXT. Other shared pages in the same file already use get_zeroed_page() correctly: drivers/infiniband/hw/bnxt_re/ib_verbs.c srq->uctx_srq_page = (void *)get_zeroed_page(GFP_KERNEL); cq->uctx_cq_page = (void *)get_zeroed_page(GFP_KERNEL); uctx->shpg is the only outlier. Bring it in line with the existing convention by switching to get_zeroed_page().

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
7.1 · CVSS 3.1
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 280 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: RDMA/bnxt_re: zero shared page before exposing to userspace bnxt_re_alloc_ucontext() allocates uctx->shpg via __get_free_page(GFP_KERNEL). The buddy allocator does not zero pages without __GFP_ZERO, so the page contains stale kernel data from whatever object most recently freed it. The page is then mapped into userspace via vm_insert_page() under BNXT_RE_MMAP_SH_PAGE in bnxt_re_mmap(). The driver only ever writes 4 bytes (a u32 AVID) at offset BNXT_RE_AVID_OFFT (0x10) inside bnxt_re_create_ah(); the remaining 4092 bytes of the page are exposed to userspace unsanitised, leaking kernel memory contents. Any user with access to /dev/infiniband/uverbsX on a host with a bnxt_re device (typically rdma group membership) can read this data via a single mmap() at pgoff 0 after IB_USER_VERBS_CMD_GET_CONTEXT. Other shared pages in the same file already use get_zeroed_page() correctly: drivers/infiniband/hw/bnxt_re/ib_verbs.c srq->uctx_srq_page = (void *)get_zeroed_page(GFP_KERNEL); cq->uctx_cq_page = (void *)get_zeroed_page(GFP_KERNEL); uctx->shpg is the only outlier. Bring it in line with the existing convention by switching to get_zeroed_page().

What

In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: zero shared page before exposing to userspace bnxt_re_alloc_ucontext() allocates uctx->shpg via __get_free_page(GFP_KERNEL). The buddy allocator does not zero pages without __GFP_ZERO, so the page contains stale kernel data from whatever object most recently freed it. The page is then mapped into userspace via vm_insert_page() under BNXT_RE_MMAP_SH_PAGE in bnxt_re_mmap(). The driver only ever writes 4 bytes (a u32 AVID) at offset BNXT_RE_AVID_OFFT (0x10) inside bnxt_re_create_ah(); the remaining 4092 bytes of the page are exposed to userspace unsanitised, leaking kernel memory contents. Any user with access to /dev/infiniband/uverbsX on a host with a bnxt_re device (typically rdma group membership) can read this data via a single mmap() at pgoff 0 after IB_USER_VERBS_CMD_GET_CONTEXT. Other shared pages in the same file already use get_zeroed_page() correctly: drivers/infiniband/hw/bnxt_re/ib_verbs.c srq->uctx_srq_page = (void *)get_zeroed_page(GFP_KERNEL); cq->uctx_cq_page = (void *)get_zeroed_page(GFP_KERNEL); uctx->shpg is the only outlier. Bring it in line with the existing convention by switching to get_zeroed_page().

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. 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: RDMA/bnxt_re: zero shared page before exposing to userspace bnxt_re_alloc_ucontext() allocates uctx->shpg via __get_free_page(GFP_KERNEL). The buddy allocator does not zero pages without __GFP_ZERO, so the page contains stale kernel data from whatever object most recently freed it. The page is then mapped into userspace via vm_insert_page() under BNXT_RE_MMAP_SH_PAGE in bnxt_re_mmap(). The driver only ever writes 4 bytes (a u32 AVID) at offset BNXT_RE_AVID_OFFT (0x10) inside bnxt_re_create_ah(); the remaining 4092 bytes of the page are exposed to userspace unsanitised, leaking kernel memory contents. Any user with access to /dev/infiniband/uverbsX on a host with a bnxt_re device (typically rdma group membership) can read this data via a single mmap() at pgoff 0 after IB_USER_VERBS_CMD_GET_CONTEXT. Other shared pages in the same file already use get_zeroed_page() correctly: drivers/infiniband/hw/bnxt_re/ib_verbs.c srq->uctx_srq_page = (void *)get_zeroed_page(GFP_KERNEL); cq->uctx_cq_page = (void *)get_zeroed_page(GFP_KERNEL); uctx->shpg is the only outlier. Bring it in line with the existing convention by switching to get_zeroed_page().

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. 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 → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
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.
CWE not yet assigned
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:N/UI:N/S:C/C:H/I:N/A:N

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.PRNonePrivileges required: The attacker does not need an account or existing 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.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
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.
Unauthenticated
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-64332Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: zero shared page before exposing to userspace bnxt_re_alloc_ucontext() allocates uctx->shpg via __get_free_page(GFP_KERNEL). The buddy allocator does not zero pages without __GFP_ZERO, so the page contains stale kernel data from whatever object most recently freed it. The page is then mapped into userspace via vm_insert_page() under BNXT_RE_MMAP_SH_PAGE in bnxt_re_mmap(). The driver only ever writes 4 bytes (a u32 AVID) at offset BNXT_RE_AVID_OFFT (0x10) inside bnxt_re_create_ah(); the remaining 4092 bytes of the page are exposed to userspace unsanitised, leaking kernel memory contents. Any user with access to /dev/infiniband/uverbsX on a host with a bnxt_re device (typically rdma group membership) can read this data via a single mmap() at pgoff 0 after IB_USER_VERBS_CMD_GET_CONTEXT. Other shared pages in the same file already use get_zeroed_page() correctly: drivers/infiniband/hw/bnxt_re/ib_verbs.c srq->uctx_srq_page = (void *)get_zeroed_page(GFP_KERNEL); cq->uctx_cq_page = (void *)get_zeroed_page(GFP_KERNEL); uctx->shpg is the only outlier. Bring it in line with the existing convention by switching to get_zeroed_page().

Official EUVD record ↗
BSI · German · WID-SEC-2026-2970Linux 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-20260826Security Bulletin 26 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 26 Aug 2026, published on 26 August 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-74398 Référence CVE CVE-2026-74401 https://www.cve.org/CVERecord?id=CVE-2026-74401 Référence CVE CVE-2026-74406 https://www.cve.org/CVERecord?id=CVE-2026-74406 Référence CVE CVE-2026-74427 https://www.cve.org/CVERecord?id=CVE-2026-74427 Référence CVE CVE-2026-74428 https://www.cve.org/CVERecord?id=CVE-2026-74428 Référence CVE CVE-2026-74433 https://www.cve.org/CVERecord?id=CVE-2026-74433 Référence CVE CVE-2026-74434 https://www.cve.org/CVERecord?id=CVE-2026-74434 Référence CVE CVE-2026-74436 https://www.cve.org/CVERecord?id=CVE-2026-74436 Référence CVE CVE-2026-74439 https://www.cve.org/CVERecord?id=CVE-2026-74439 Référence CVE CVE-2026-74584 https://www.cve.org/CVERecord?id=CVE-2026-74584 Référence CVE CVE-2026-80591 https://www.cve.org/CVERecord?id=CVE-2026-80591 Référence CVE CVE-2026-80665 https://www.cve.org/CVERecord?id=CVE-2026-80665 Gestion détaillée du document le 02 octobre 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 systèmes d'information

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

d?id=CVE-2026-74556 Référence CVE CVE-2026-74557 https://www.cve.org/CVERecord?id=CVE-2026-74557 Référence CVE CVE-2026-74563 https://www.cve.org/CVERecord?id=CVE-2026-74563 Référence CVE CVE-2026-74566 https://www.cve.org/CVERecord?id=CVE-2026-74566 Référence CVE CVE-2026-74567 https://www.cve.org/CVERecord?id=CVE-2026-74567 Référence CVE CVE-2026-74571 https://www.cve.org/CVERecord?id=CVE-2026-74571 Référence CVE CVE-2026-74577 https://www.cve.org/CVERecord?id=CVE-2026-74577 Référence CVE CVE-2026-74581 https://www.cve.org/CVERecord?id=CVE-2026-74581 Référence CVE CVE-2026-74582 https://www.cve.org/CVERecord?id=CVE-2026-74582 Référence CVE CVE-2026-74584 https://www.cve.org/CVERecord?id=CVE-2026-74584 Référence CVE CVE-2026-74598 https://www.cve.org/CVERecord?id=CVE-2026-74598 Référence CVE CVE-2026-74610 https://www.cve.org/CVERecord?id=CVE-2026-74610 Référence CVE CVE-2026-74612 https://www.cve.org/CVERecord?id=CVE-2026-74612 Référence CVE CVE-2026-74615 https://www.cve.org/CVERecord?id=CVE-2026-74615 Référence CVE CVE-2026-74616 https://www.cve.org/CVERecord?id=CVE-2026-74616 Référence CVE CVE-2026-74622 https://www.cve.org/CVERecord?id=CVE-2026-74622 Référence CVE CVE-2026-74644 https://www.cve.org/CVERecord?id=CVE-2026-74644 Référence CVE CVE-2026-74665 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-74518 Référence CVE CVE-2026-74519 https://www.cve.org/CVERecord?id=CVE-2026-74519 Référence CVE CVE-2026-74537 https://www.cve.org/CVERecord?id=CVE-2026-74537 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74550 https://www.cve.org/CVERecord?id=CVE-2026-74550 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74557 https://www.cve.org/CVERecord?id=CVE-2026-74557 Référence CVE CVE-2026-74581 https://www.cve.org/CVERecord?id=CVE-2026-74581 Référence CVE CVE-2026-74582 https://www.cve.org/CVERecord?id=CVE-2026-74582 Référence CVE CVE-2026-74584 https://www.cve.org/CVERecord?id=CVE-2026-74584 Référence CVE CVE-2026-74615 https://www.cve.org/CVERecord?id=CVE-2026-74615 Référence CVE CVE-2026-74616 https://www.cve.org/CVERecord?id=CVE-2026-74616 Référence CVE CVE-2026-74669 https://www.cve.org/CVERecord?id=CVE-2026-74669 Référence CVE CVE-2026-74673 https://www.cve.org/CVERecord?id=CVE-2026-74673 Référence CVE CVE-2026-74695 https://www.cve.org/CVERecord?id=CVE-2026-74695 Référence CVE CVE-2026-74705 https://www.cve.org/CVERecord?id=CVE-2026-74705 Référence CVE CVE-2026-74743 https://www.cve.org/CVERecord?id=CVE-2026-74743 Référence CVE CVE-2026-80534 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-74398 Référence CVE CVE-2026-74401 https://www.cve.org/CVERecord?id=CVE-2026-74401 Référence CVE CVE-2026-74406 https://www.cve.org/CVERecord?id=CVE-2026-74406 Référence CVE CVE-2026-74427 https://www.cve.org/CVERecord?id=CVE-2026-74427 Référence CVE CVE-2026-74428 https://www.cve.org/CVERecord?id=CVE-2026-74428 Référence CVE CVE-2026-74433 https://www.cve.org/CVERecord?id=CVE-2026-74433 Référence CVE CVE-2026-74434 https://www.cve.org/CVERecord?id=CVE-2026-74434 Référence CVE CVE-2026-74436 https://www.cve.org/CVERecord?id=CVE-2026-74436 Référence CVE CVE-2026-74439 https://www.cve.org/CVERecord?id=CVE-2026-74439 Référence CVE CVE-2026-74584 https://www.cve.org/CVERecord?id=CVE-2026-74584 Référence CVE CVE-2026-80591 https://www.cve.org/CVERecord?id=CVE-2026-80591 Référence CVE CVE-2026-80665 https://www.cve.org/CVERecord?id=CVE-2026-80665 Référence CVE CVE-2026-80952 https://www.cve.org/CVERecord?id=CVE-2026-80952 Référence CVE CVE-2026-90386 https://www.cve.org/CVERecord?id=CVE-2026-90386 Gestion détaillée du document le 25 septembre 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

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

d?id=CVE-2026-74550 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74563 https://www.cve.org/CVERecord?id=CVE-2026-74563 Référence CVE CVE-2026-74566 https://www.cve.org/CVERecord?id=CVE-2026-74566 Référence CVE CVE-2026-74567 https://www.cve.org/CVERecord?id=CVE-2026-74567 Référence CVE CVE-2026-74571 https://www.cve.org/CVERecord?id=CVE-2026-74571 Référence CVE CVE-2026-74577 https://www.cve.org/CVERecord?id=CVE-2026-74577 Référence CVE CVE-2026-74581 https://www.cve.org/CVERecord?id=CVE-2026-74581 Référence CVE CVE-2026-74582 https://www.cve.org/CVERecord?id=CVE-2026-74582 Référence CVE CVE-2026-74584 https://www.cve.org/CVERecord?id=CVE-2026-74584 Référence CVE CVE-2026-74610 https://www.cve.org/CVERecord?id=CVE-2026-74610 Référence CVE CVE-2026-74669 https://www.cve.org/CVERecord?id=CVE-2026-74669 Référence CVE CVE-2026-74692 https://www.cve.org/CVERecord?id=CVE-2026-74692 Référence CVE CVE-2026-74694 https://www.cve.org/CVERecord?id=CVE-2026-74694 Référence CVE CVE-2026-74695 https://www.cve.org/CVERecord?id=CVE-2026-74695 Référence CVE CVE-2026-74712 https://www.cve.org/CVERecord?id=CVE-2026-74712 Référence CVE CVE-2026-74717 https://www.cve.org/CVERecord?id=CVE-2026-74717 Référence CVE CVE-2026-74722 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-74478 Référence CVE CVE-2026-74480 https://www.cve.org/CVERecord?id=CVE-2026-74480 Référence CVE CVE-2026-74493 https://www.cve.org/CVERecord?id=CVE-2026-74493 Référence CVE CVE-2026-74495 https://www.cve.org/CVERecord?id=CVE-2026-74495 Référence CVE CVE-2026-74521 https://www.cve.org/CVERecord?id=CVE-2026-74521 Référence CVE CVE-2026-74538 https://www.cve.org/CVERecord?id=CVE-2026-74538 Référence CVE CVE-2026-74541 https://www.cve.org/CVERecord?id=CVE-2026-74541 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74569 https://www.cve.org/CVERecord?id=CVE-2026-74569 Référence CVE CVE-2026-74584 https://www.cve.org/CVERecord?id=CVE-2026-74584 Référence CVE CVE-2026-80591 https://www.cve.org/CVERecord?id=CVE-2026-80591 Gestion détaillée du document le 18 septembre 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 systèmes d'information

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

d?id=CVE-2026-68088 Référence CVE CVE-2026-68089 https://www.cve.org/CVERecord?id=CVE-2026-68089 Référence CVE CVE-2026-68090 https://www.cve.org/CVERecord?id=CVE-2026-68090 Référence CVE CVE-2026-68091 https://www.cve.org/CVERecord?id=CVE-2026-68091 Référence CVE CVE-2026-68092 https://www.cve.org/CVERecord?id=CVE-2026-68092 Référence CVE CVE-2026-68372 https://www.cve.org/CVERecord?id=CVE-2026-68372 Référence CVE CVE-2026-68459 https://www.cve.org/CVERecord?id=CVE-2026-68459 Référence CVE CVE-2026-68460 https://www.cve.org/CVERecord?id=CVE-2026-68460 Référence CVE CVE-2026-68461 https://www.cve.org/CVERecord?id=CVE-2026-68461 Référence CVE CVE-2026-74584 https://www.cve.org/CVERecord?id=CVE-2026-74584 Référence CVE CVE-2026-80591 https://www.cve.org/CVERecord?id=CVE-2026-80591 Gestion détaillée du document le 11 septembre 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 systèmes d'information

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

d?id=CVE-2026-74550 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74563 https://www.cve.org/CVERecord?id=CVE-2026-74563 Référence CVE CVE-2026-74566 https://www.cve.org/CVERecord?id=CVE-2026-74566 Référence CVE CVE-2026-74567 https://www.cve.org/CVERecord?id=CVE-2026-74567 Référence CVE CVE-2026-74571 https://www.cve.org/CVERecord?id=CVE-2026-74571 Référence CVE CVE-2026-74577 https://www.cve.org/CVERecord?id=CVE-2026-74577 Référence CVE CVE-2026-74581 https://www.cve.org/CVERecord?id=CVE-2026-74581 Référence CVE CVE-2026-74582 https://www.cve.org/CVERecord?id=CVE-2026-74582 Référence CVE CVE-2026-74584 https://www.cve.org/CVERecord?id=CVE-2026-74584 Référence CVE CVE-2026-74610 https://www.cve.org/CVERecord?id=CVE-2026-74610 Référence CVE CVE-2026-74669 https://www.cve.org/CVERecord?id=CVE-2026-74669 Référence CVE CVE-2026-74692 https://www.cve.org/CVERecord?id=CVE-2026-74692 Référence CVE CVE-2026-74694 https://www.cve.org/CVERecord?id=CVE-2026-74694 Référence CVE CVE-2026-74695 https://www.cve.org/CVERecord?id=CVE-2026-74695 Référence CVE CVE-2026-74712 https://www.cve.org/CVERecord?id=CVE-2026-74712 Référence CVE CVE-2026-74717 https://www.cve.org/CVERecord?id=CVE-2026-74717 Référence CVE CVE-2026-74722 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
Fixed
Linux: < 4.11, 5.10.260 ≤ 5.10.*, 5.15.211 ≤ 5.15.*, 6.1.177 ≤ 6.1.*, 6.6.144 ≤ 6.6.*, 6.12.95 ≤ 6.12.*, 6.18.37 ≤ 6.18.*, 7.0.14 ≤ 7.0.*, 7.1 ≤ *
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 22 Aug 2026 · Last source change 25 Aug 2026, 05:40 UTC · CWE not yet assigned

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-23
European sourceENISA EUVD · EUVD-2026-64332
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CNA ↗
  2. CVSS scoreCVSS score changed from not recorded to 7.1 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N).
    Before
    not recorded
    After
    7.1 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N)
    CNA ↗
  3. ENISA EUVD mappingEUVD-2026-64332 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-64332"}
    ENISA EUVD ↗
  4. Catalogue recordCVE added to the BlackTree catalogue.
    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-64332↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-74584 · cve.blacktree.nl