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

RDMA/nldev: Fix locking when accessing mr->pd

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 295 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.13% 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 295 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.

25 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 21 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.111-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.111-1~deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-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-74334 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-74334
270 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 Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: RDMA/nldev: Fix locking when accessing mr->pd Sashiko points out that, due to rereg_mr, the PD is actually variable and all the touches in nldev are racy. Use mr->device instead of mr->pd->device. Getting the PD restrack ID is more tricky. To avoid disturbing all the happy paths, add an rdma_restrack_sync() operation which is sort of like flush_workqueue() or synchronize_irq(): after it returns, all the old nldev touches to the mr are gone and everything sees the new PD. This makes it safe to reach into the PD pointer.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-74334 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: RDMA/nldev: Fix locking when accessing mr->pd
274 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 RDMA/nldev component of the Linux kernel. Improper locking during memory region re-registration (rereg_mr) can lead to a race condition when accessing protection domains (PD). This vulnerability could result in unpredictable system behavior or a denial of service due to concurrent, unsynchronized memory access.
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-59481

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: RDMA/nldev: Fix locking when accessing mr->pd Sashiko points out that, due to rereg_mr, the PD is actually variable and all the touches in nldev are racy. Use mr->device instead of mr->pd->device. Getting the PD restrack ID is more tricky. To avoid disturbing all the happy paths, add an rdma_restrack_sync() operation which is sort of like flush_workqueue() or synchronize_irq(): after it returns, all the old nldev touches to the mr are gone and everything sees the new PD. This makes it safe to reach into the PD pointer.

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.8 · 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 295 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/nldev: Fix locking when accessing mr->pd Sashiko points out that, due to rereg_mr, the PD is actually variable and all the touches in nldev are racy. Use mr->device instead of mr->pd->device. Getting the PD restrack ID is more tricky. To avoid disturbing all the happy paths, add an rdma_restrack_sync() operation which is sort of like flush_workqueue() or synchronize_irq(): after it returns, all the old nldev touches to the mr are gone and everything sees the new PD. This makes it safe to reach into the PD pointer.

What

In the Linux kernel, the following vulnerability has been resolved: RDMA/nldev: Fix locking when accessing mr->pd Sashiko points out that, due to rereg_mr, the PD is actually variable and all the touches in nldev are racy. Use mr->device instead of mr->pd->device. Getting the PD restrack ID is more tricky. To avoid disturbing all the happy paths, add an rdma_restrack_sync() operation which is sort of like flush_workqueue() or synchronize_irq(): after it returns, all the old nldev touches to the mr are gone and everything sees the new PD. This makes it safe to reach into the PD pointer.

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 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: RDMA/nldev: Fix locking when accessing mr->pd Sashiko points out that, due to rereg_mr, the PD is actually variable and all the touches in nldev are racy. Use mr->device instead of mr->pd->device. Getting the PD restrack ID is more tricky. To avoid disturbing all the happy paths, add an rdma_restrack_sync() operation which is sort of like flush_workqueue() or synchronize_irq(): after it returns, all the old nldev touches to the mr are gone and everything sees the new PD. This makes it safe to reach into the PD pointer.

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 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 → vulnerable operation → 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.
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: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.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-59481Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: RDMA/nldev: Fix locking when accessing mr->pd Sashiko points out that, due to rereg_mr, the PD is actually variable and all the touches in nldev are racy. Use mr->device instead of mr->pd->device. Getting the PD restrack ID is more tricky. To avoid disturbing all the happy paths, add an rdma_restrack_sync() operation which is sort of like flush_workqueue() or synchronize_irq(): after it returns, all the old nldev touches to the mr are gone and everything sees the new PD. This makes it safe to reach into the PD pointer.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2852Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260819Security Bulletin 19 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 19 Aug 2026, published on 19 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-1253Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2026-72413 Référence CVE CVE-2026-72438 https://www.cve.org/CVERecord?id=CVE-2026-72438 Référence CVE CVE-2026-72485 https://www.cve.org/CVERecord?id=CVE-2026-72485 Référence CVE CVE-2026-72496 https://www.cve.org/CVERecord?id=CVE-2026-72496 Référence CVE CVE-2026-74258 https://www.cve.org/CVERecord?id=CVE-2026-74258 Référence CVE CVE-2026-74268 https://www.cve.org/CVERecord?id=CVE-2026-74268 Référence CVE CVE-2026-74289 https://www.cve.org/CVERecord?id=CVE-2026-74289 Référence CVE CVE-2026-74291 https://www.cve.org/CVERecord?id=CVE-2026-74291 Référence CVE CVE-2026-74294 https://www.cve.org/CVERecord?id=CVE-2026-74294 Référence CVE CVE-2026-74334 https://www.cve.org/CVERecord?id=CVE-2026-74334 Référence CVE CVE-2026-74496 https://www.cve.org/CVERecord?id=CVE-2026-74496 Référence CVE CVE-2026-74521 https://www.cve.org/CVERecord?id=CVE-2026-74521 Référence CVE CVE-2026-74735 https://www.cve.org/CVERecord?id=CVE-2026-74735 Référence CVE CVE-2026-74753 https://www.cve.org/CVERecord?id=CVE-2026-74753 Référence CVE CVE-2026-80521 https://www.cve.org/CVERecord?id=CVE-2026-80521 Référence CVE CVE-2026-80671 https://www.cve.org/CVERecord?id=CVE-2026-80671 Référence CVE CVE-2026-80755 https://www.cve.org/CVERecord?id=CVE-2026-80755 Référence CVE CVE-2026-80762 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-74296 Référence CVE CVE-2026-74297 https://www.cve.org/CVERecord?id=CVE-2026-74297 Référence CVE CVE-2026-74307 https://www.cve.org/CVERecord?id=CVE-2026-74307 Référence CVE CVE-2026-74308 https://www.cve.org/CVERecord?id=CVE-2026-74308 Référence CVE CVE-2026-74313 https://www.cve.org/CVERecord?id=CVE-2026-74313 Référence CVE CVE-2026-74316 https://www.cve.org/CVERecord?id=CVE-2026-74316 Référence CVE CVE-2026-74317 https://www.cve.org/CVERecord?id=CVE-2026-74317 Référence CVE CVE-2026-74318 https://www.cve.org/CVERecord?id=CVE-2026-74318 Référence CVE CVE-2026-74321 https://www.cve.org/CVERecord?id=CVE-2026-74321 Référence CVE CVE-2026-74334 https://www.cve.org/CVERecord?id=CVE-2026-74334 Référence CVE CVE-2026-74345 https://www.cve.org/CVERecord?id=CVE-2026-74345 Référence CVE CVE-2026-74346 https://www.cve.org/CVERecord?id=CVE-2026-74346 Référence CVE CVE-2026-74349 https://www.cve.org/CVERecord?id=CVE-2026-74349 Référence CVE CVE-2026-74363 https://www.cve.org/CVERecord?id=CVE-2026-74363 Référence CVE CVE-2026-74375 https://www.cve.org/CVERecord?id=CVE-2026-74375 Référence CVE CVE-2026-74377 https://www.cve.org/CVERecord?id=CVE-2026-74377 Référence CVE CVE-2026-74378 https://www.cve.org/CVERecord?id=CVE-2026-74378 Référence CVE CVE-2026-74382 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-74255 Référence CVE CVE-2026-74261 https://www.cve.org/CVERecord?id=CVE-2026-74261 Référence CVE CVE-2026-74265 https://www.cve.org/CVERecord?id=CVE-2026-74265 Référence CVE CVE-2026-74271 https://www.cve.org/CVERecord?id=CVE-2026-74271 Référence CVE CVE-2026-74278 https://www.cve.org/CVERecord?id=CVE-2026-74278 Référence CVE CVE-2026-74279 https://www.cve.org/CVERecord?id=CVE-2026-74279 Référence CVE CVE-2026-74296 https://www.cve.org/CVERecord?id=CVE-2026-74296 Référence CVE CVE-2026-74297 https://www.cve.org/CVERecord?id=CVE-2026-74297 Référence CVE CVE-2026-74302 https://www.cve.org/CVERecord?id=CVE-2026-74302 Référence CVE CVE-2026-74334 https://www.cve.org/CVERecord?id=CVE-2026-74334 Référence CVE CVE-2026-74341 https://www.cve.org/CVERecord?id=CVE-2026-74341 Référence CVE CVE-2026-74345 https://www.cve.org/CVERecord?id=CVE-2026-74345 Référence CVE CVE-2026-74377 https://www.cve.org/CVERecord?id=CVE-2026-74377 Référence CVE CVE-2026-74378 https://www.cve.org/CVERecord?id=CVE-2026-74378 Référence CVE CVE-2026-74382 https://www.cve.org/CVERecord?id=CVE-2026-74382 Référence CVE CVE-2026-74388 https://www.cve.org/CVERecord?id=CVE-2026-74388 Référence CVE CVE-2026-74390 https://www.cve.org/CVERecord?id=CVE-2026-74390 Référence CVE CVE-2026-74394 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-72499 Référence CVE CVE-2026-72500 https://www.cve.org/CVERecord?id=CVE-2026-72500 Référence CVE CVE-2026-72501 https://www.cve.org/CVERecord?id=CVE-2026-72501 Référence CVE CVE-2026-72502 https://www.cve.org/CVERecord?id=CVE-2026-72502 Référence CVE CVE-2026-74269 https://www.cve.org/CVERecord?id=CVE-2026-74269 Référence CVE CVE-2026-74296 https://www.cve.org/CVERecord?id=CVE-2026-74296 Référence CVE CVE-2026-74297 https://www.cve.org/CVERecord?id=CVE-2026-74297 Référence CVE CVE-2026-74318 https://www.cve.org/CVERecord?id=CVE-2026-74318 Référence CVE CVE-2026-74321 https://www.cve.org/CVERecord?id=CVE-2026-74321 Référence CVE CVE-2026-74334 https://www.cve.org/CVERecord?id=CVE-2026-74334 Référence CVE CVE-2026-74345 https://www.cve.org/CVERecord?id=CVE-2026-74345 Référence CVE CVE-2026-74394 https://www.cve.org/CVERecord?id=CVE-2026-74394 Référence CVE CVE-2026-74395 https://www.cve.org/CVERecord?id=CVE-2026-74395 Référence CVE CVE-2026-74454 https://www.cve.org/CVERecord?id=CVE-2026-74454 Référence CVE CVE-2026-74474 https://www.cve.org/CVERecord?id=CVE-2026-74474 Référence CVE CVE-2026-74481 https://www.cve.org/CVERecord?id=CVE-2026-74481 Référence CVE CVE-2026-74482 https://www.cve.org/CVERecord?id=CVE-2026-74482 Référence CVE CVE-2026-74488 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-72499 Référence CVE CVE-2026-72500 https://www.cve.org/CVERecord?id=CVE-2026-72500 Référence CVE CVE-2026-72501 https://www.cve.org/CVERecord?id=CVE-2026-72501 Référence CVE CVE-2026-72502 https://www.cve.org/CVERecord?id=CVE-2026-72502 Référence CVE CVE-2026-74269 https://www.cve.org/CVERecord?id=CVE-2026-74269 Référence CVE CVE-2026-74296 https://www.cve.org/CVERecord?id=CVE-2026-74296 Référence CVE CVE-2026-74297 https://www.cve.org/CVERecord?id=CVE-2026-74297 Référence CVE CVE-2026-74318 https://www.cve.org/CVERecord?id=CVE-2026-74318 Référence CVE CVE-2026-74321 https://www.cve.org/CVERecord?id=CVE-2026-74321 Référence CVE CVE-2026-74334 https://www.cve.org/CVERecord?id=CVE-2026-74334 Référence CVE CVE-2026-74345 https://www.cve.org/CVERecord?id=CVE-2026-74345 Référence CVE CVE-2026-74394 https://www.cve.org/CVERecord?id=CVE-2026-74394 Référence CVE CVE-2026-74395 https://www.cve.org/CVERecord?id=CVE-2026-74395 Référence CVE CVE-2026-74454 https://www.cve.org/CVERecord?id=CVE-2026-74454 Référence CVE CVE-2026-74474 https://www.cve.org/CVERecord?id=CVE-2026-74474 Référence CVE CVE-2026-74481 https://www.cve.org/CVERecord?id=CVE-2026-74481 Référence CVE CVE-2026-74482 https://www.cve.org/CVERecord?id=CVE-2026-74482 Référence CVE CVE-2026-74488 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.18, 6.1.188 ≤ 6.1.*, 6.6.157 ≤ 6.6.*, 6.12.110 ≤ 6.12.*, 6.18.52 ≤ 6.18.*, 7.1.5 ≤ 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 15 Aug 2026 · Last source change 14 Sept 2026, 11:58 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-59481
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. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/845c6b355226195dad1f26b300c4830f57034e8b; removed remediation: git.kernel.org/1a132ee4e655288d9a0937ea5109a0d038431ae9.
    Before
    remediation: git.kernel.org/1a132ee4e655288d9a0937ea5109a0d038431ae9
    After
    remediation: git.kernel.org/845c6b355226195dad1f26b300c4830f57034e8b
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    da5c8507821573b8ed6e3f47e009f273493ffaf7 < 1a132ee4e655288d9a0937ea5109a0d038431ae9; da5c8507821573b8ed6e3f47e009f273493ffaf7 < 50d5c02ab8e62325548bd3a6e6b758a9dcd6e7c3; 4.18 · Fixed: < 4.18; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    After
    Linux: da5c8507821573b8ed6e3f47e009f273493ffaf7 < 845c6b355226195dad1f26b300c4830f57034e8b, da5c8507821573b8ed6e3f47e009f273493ffaf7 < 7a0cbb5721a1da81e902d73b6049f85ca8f3fc0a, da5c8507821573b8ed6e3f47e009f273493ffaf7 < 05e26f34597e9c38bb5b340d86b179b23673869f, da5c8507821573b8ed6e3f47e009f273493ffaf7 < a07cba1296aaa81bf9b914486ca957aaff196247, da5c8507821573b8ed6e3f47e009f273493ffaf7 < 1a132ee4e655288d9a0937ea5109a0d038431ae9, da5c8507821573b8ed6e3f47e009f273493ffaf7 < 50d5c02ab8e62325548bd3a6e6b758a9dcd6e7c3, 4.18 · Fixed: Linux: < 4.18, 6.1.188 ≤ 6.1.*, 6.6.157 ≤ 6.6.*, 6.12.110 ≤ 6.12.*, 6.18.52 ≤ 6.18.*, 7.1.5 ≤ 7.1.*, 7.2 ≤ *
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    da5c8507821573b8ed6e3f47e009f273493ffaf7 < 1a132ee4e655288d9a0937ea5109a0d038431ae9; da5c8507821573b8ed6e3f47e009f273493ffaf7 < 50d5c02ab8e62325548bd3a6e6b758a9dcd6e7c3; 4.18 · Fixed: < 4.18; 7.1.5 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    da5c8507821573b8ed6e3f47e009f273493ffaf7 < 1a132ee4e655288d9a0937ea5109a0d038431ae9; da5c8507821573b8ed6e3f47e009f273493ffaf7 < 50d5c02ab8e62325548bd3a6e6b758a9dcd6e7c3; 4.18 · Fixed: < 4.18; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  4. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CNA ↗
  5. CVSS scoreCVSS score changed from not recorded to 7.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    7.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
    CNA ↗
  6. 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-59481↗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-74334 · cve.blacktree.nl