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

net: bridge: use a stable FDB dst snapshot in RCU readers

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 25 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 8 Sep 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: No default targetRemediation target: Normal maintenance

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 25 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.86-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.4-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-46086 · CSAF 2.0 · revision 19 · interimSUSE Product Security TeamCVE-2026-46086
201 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
Summary
In the Linux kernel, the following vulnerability has been resolved: net: bridge: use a stable FDB dst snapshot in RCU readers Local FDB entries can be rewritten in place by `fdb_delete_local()`, which updates `f->dst` to another port or to `NULL` while keeping the entry alive. Several bridge RCU readers inspect `f->dst`, including `br_fdb_fillbuf()` through the `brforward_read()` sysfs path. These readers currently load `f->dst` multiple times and can therefore observe inconsistent values across the check and later dereference. In `br_fdb_fillbuf()`, this means a concurrent local-FDB update can change `f->dst` after the NULL check and before the `port_no` dereference, leading to a NULL-ptr-deref. Fix this by taking a single `READ_ONCE()` snapshot of `f->dst` in each affected RCU reader and using that snapshot for the rest of the access sequence. Also publish the in-place `f->dst` updates in `fdb_delete_local()` with `WRITE_ONCE()` so the readers and writer use matching access patterns.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: net: bridge: use a stable FDB dst snapshot in RCU readers Local FDB entries can be rewritten in place by `fdb_delete_local()`, which updates `f->dst` to another port or to `NULL` while keeping the entry alive. Several bridge RCU readers inspect `f->dst`, including `br_fdb_fillbuf()` through the `brforward_read()` sysfs path. These readers currently load `f->dst` multiple times and can therefore observe inconsistent values across the check and later dereference. In `br_fdb_fillbuf()`, this means a concurrent local-FDB update can change `f->dst` after the NULL check and before the `port_no` dereference, leading to a NULL-ptr-deref. Fix this by taking a single `READ_ONCE()` snapshot of `f->dst` in each affected RCU reader and using that snapshot for the rest of the access sequence. Also publish the in-place `f->dst` updates in `fdb_delete_local()` with `WRITE_ONCE()` so the readers and writer use matching access patterns.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-32469

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net: bridge: use a stable FDB dst snapshot in RCU readers Local FDB entries can be rewritten in place by `fdb_delete_local()`, which updates `f->dst` to another port or to `NULL` while keeping the entry alive. Several bridge RCU readers inspect `f->dst`, including `br_fdb_fillbuf()` through the `brforward_read()` sysfs path. These readers currently load `f->dst` multiple times and can therefore observe inconsistent values across the check and later dereference. In `br_fdb_fillbuf()`, this means a concurrent local-FDB update can change `f->dst` after the NULL check and before the `port_no` dereference, leading to a NULL-ptr-deref. Fix this by taking a single `READ_ONCE()` snapshot of `f->dst` in each affected RCU reader and using that snapshot for the rest of the access sequence. Also publish the in-place `f->dst` updates in `fdb_delete_local()` with `WRITE_ONCE()` so the readers and writer use matching access patterns.

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
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 25 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: net: bridge: use a stable FDB dst snapshot in RCU readers Local FDB entries can be rewritten in place by `fdb_delete_local()`, which updates `f->dst` to another port or to `NULL` while keeping the entry alive. Several bridge RCU readers inspect `f->dst`, including `br_fdb_fillbuf()` through the `brforward_read()` sysfs path. These readers currently load `f->dst` multiple times and can therefore observe inconsistent values across the check and later dereference. In `br_fdb_fillbuf()`, this means a concurrent local-FDB update can change `f->dst` after the NULL check and before the `port_no` dereference, leading to a NULL-ptr-deref. Fix this by taking a single `READ_ONCE()` snapshot of `f->dst` in each affected RCU reader and using that snapshot for the rest of the access sequence. Also publish the in-place `f->dst` updates in `fdb_delete_local()` with `WRITE_ONCE()` so the readers and writer use matching access patterns.

What

In the Linux kernel, the following vulnerability has been resolved: net: bridge: use a stable FDB dst snapshot in RCU readers Local FDB entries can be rewritten in place by `fdb_delete_local()`, which updates `f->dst` to another port or to `NULL` while keeping the entry alive. Several bridge RCU readers inspect `f->dst`, including `br_fdb_fillbuf()` through the `brforward_read()` sysfs path. These readers currently load `f->dst` multiple times and can therefore observe inconsistent values across the check and later dereference. In `br_fdb_fillbuf()`, this means a concurrent local-FDB update can change `f->dst` after the NULL check and before the `port_no` dereference, leading to a NULL-ptr-deref. Fix this by taking a single `READ_ONCE()` snapshot of `f->dst` in each affected RCU reader and using that snapshot for the rest of the access sequence. Also publish the in-place `f->dst` updates in `fdb_delete_local()` with `WRITE_ONCE()` so the readers and writer use matching access patterns.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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: net: bridge: use a stable FDB dst snapshot in RCU readers Local FDB entries can be rewritten in place by `fdb_delete_local()`, which updates `f->dst` to another port or to `NULL` while keeping the entry alive. Several bridge RCU readers inspect `f->dst`, including `br_fdb_fillbuf()` through the `brforward_read()` sysfs path. These readers currently load `f->dst` multiple times and can therefore observe inconsistent values across the check and later dereference. In `br_fdb_fillbuf()`, this means a concurrent local-FDB update can change `f->dst` after the NULL check and before the `port_no` dereference, leading to a NULL-ptr-deref. Fix this by taking a single `READ_ONCE()` snapshot of `f->dst` in each affected RCU reader and using that snapshot for the rest of the access sequence. Also publish the in-place `f->dst` updates in `fdb_delete_local()` with `WRITE_ONCE()` so the readers and writer use matching access patterns.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-476
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-32469Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net: bridge: use a stable FDB dst snapshot in RCU readers Local FDB entries can be rewritten in place by `fdb_delete_local()`, which updates `f->dst` to another port or to `NULL` while keeping the entry alive. Several bridge RCU readers inspect `f->dst`, including `br_fdb_fillbuf()` through the `brforward_read()` sysfs path. These readers currently load `f->dst` multiple times and can therefore observe inconsistent values across the check and later dereference. In `br_fdb_fillbuf()`, this means a concurrent local-FDB update can change `f->dst` after the NULL check and before the `port_no` dereference, leading to a NULL-ptr-deref. Fix this by taking a single `READ_ONCE()` snapshot of `f->dst` in each affected RCU reader and using that snapshot for the rest of the access sequence. Also publish the in-place `f->dst` updates in `fdb_delete_local()` with `WRITE_ONCE()` so the readers and writer use matching access patterns.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3623IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen, einen Denial-of-Service-Zustand auszulösen oder Cross-Site-Scripting-Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-3043IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um beliebigen Programmcode auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-1700Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

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

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1094Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2026-45149 Référence CVE CVE-2026-45249 https://www.cve.org/CVERecord?id=CVE-2026-45249 Référence CVE CVE-2026-4539 https://www.cve.org/CVERecord?id=CVE-2026-4539 Référence CVE CVE-2026-45505 https://www.cve.org/CVERecord?id=CVE-2026-45505 Référence CVE CVE-2026-45736 https://www.cve.org/CVERecord?id=CVE-2026-45736 Référence CVE CVE-2026-45740 https://www.cve.org/CVERecord?id=CVE-2026-45740 Référence CVE CVE-2026-45822 https://www.cve.org/CVERecord?id=CVE-2026-45822 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-46054 https://www.cve.org/CVERecord?id=CVE-2026-46054 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46117 https://www.cve.org/CVERecord?id=CVE-2026-46117 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46145 https://www.cve.org/CVERecord?id=CVE-2026-46145 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46189 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-46075 Référence CVE CVE-2026-46076 https://www.cve.org/CVERecord?id=CVE-2026-46076 Référence CVE CVE-2026-46077 https://www.cve.org/CVERecord?id=CVE-2026-46077 Référence CVE CVE-2026-46078 https://www.cve.org/CVERecord?id=CVE-2026-46078 Référence CVE CVE-2026-46079 https://www.cve.org/CVERecord?id=CVE-2026-46079 Référence CVE CVE-2026-46080 https://www.cve.org/CVERecord?id=CVE-2026-46080 Référence CVE CVE-2026-46082 https://www.cve.org/CVERecord?id=CVE-2026-46082 Référence CVE CVE-2026-46083 https://www.cve.org/CVERecord?id=CVE-2026-46083 Référence CVE CVE-2026-46084 https://www.cve.org/CVERecord?id=CVE-2026-46084 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46088 https://www.cve.org/CVERecord?id=CVE-2026-46088 Référence CVE CVE-2026-46089 https://www.cve.org/CVERecord?id=CVE-2026-46089 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 Référence CVE CVE-2026-46092 https://www.cve.org/CVERecord?id=CVE-2026-46092 Référence CVE CVE-2026-46094 https://www.cve.org/CVERecord?id=CVE-2026-46094 Référence CVE CVE-2026-46098 https://www.cve.org/CVERecord?id=CVE-2026-46098 Référence CVE CVE-2026-46099 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46064 Référence CVE CVE-2026-46068 https://www.cve.org/CVERecord?id=CVE-2026-46068 Référence CVE CVE-2026-46073 https://www.cve.org/CVERecord?id=CVE-2026-46073 Référence CVE CVE-2026-46074 https://www.cve.org/CVERecord?id=CVE-2026-46074 Référence CVE CVE-2026-46075 https://www.cve.org/CVERecord?id=CVE-2026-46075 Référence CVE CVE-2026-46077 https://www.cve.org/CVERecord?id=CVE-2026-46077 Référence CVE CVE-2026-46080 https://www.cve.org/CVERecord?id=CVE-2026-46080 Référence CVE CVE-2026-46082 https://www.cve.org/CVERecord?id=CVE-2026-46082 Référence CVE CVE-2026-46084 https://www.cve.org/CVERecord?id=CVE-2026-46084 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46088 https://www.cve.org/CVERecord?id=CVE-2026-46088 Référence CVE CVE-2026-46089 https://www.cve.org/CVERecord?id=CVE-2026-46089 Référence CVE CVE-2026-46092 https://www.cve.org/CVERecord?id=CVE-2026-46092 Référence CVE CVE-2026-46096 https://www.cve.org/CVERecord?id=CVE-2026-46096 Référence CVE CVE-2026-46102 https://www.cve.org/CVERecord?id=CVE-2026-46102 Référence CVE CVE-2026-46103 https://www.cve.org/CVERecord?id=CVE-2026-46103 Référence CVE CVE-2026-46108 https://www.cve.org/CVERecord?id=CVE-2026-46108 Référence CVE CVE-2026-46109 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46040 Référence CVE CVE-2026-46049 https://www.cve.org/CVERecord?id=CVE-2026-46049 Référence CVE CVE-2026-46051 https://www.cve.org/CVERecord?id=CVE-2026-46051 Référence CVE CVE-2026-46052 https://www.cve.org/CVERecord?id=CVE-2026-46052 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46064 https://www.cve.org/CVERecord?id=CVE-2026-46064 Référence CVE CVE-2026-46068 https://www.cve.org/CVERecord?id=CVE-2026-46068 Référence CVE CVE-2026-46080 https://www.cve.org/CVERecord?id=CVE-2026-46080 Référence CVE CVE-2026-46084 https://www.cve.org/CVERecord?id=CVE-2026-46084 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46088 https://www.cve.org/CVERecord?id=CVE-2026-46088 Référence CVE CVE-2026-46102 https://www.cve.org/CVERecord?id=CVE-2026-46102 Référence CVE CVE-2026-46109 https://www.cve.org/CVERecord?id=CVE-2026-46109 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46117 https://www.cve.org/CVERecord?id=CVE-2026-46117 Référence CVE CVE-2026-46126 https://www.cve.org/CVERecord?id=CVE-2026-46126 Référence CVE CVE-2026-46144 https://www.cve.org/CVERecord?id=CVE-2026-46144 Référence CVE CVE-2026-46145 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-12505 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=CVE-2026-31488 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31684 https://www.cve.org/CVERecord?id=CVE-2026-31684 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52950 https://www.cve.org/CVERecord?id=CVE-2026-52950 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-52993 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-46077 Référence CVE CVE-2026-46078 https://www.cve.org/CVERecord?id=CVE-2026-46078 Référence CVE CVE-2026-46079 https://www.cve.org/CVERecord?id=CVE-2026-46079 Référence CVE CVE-2026-46080 https://www.cve.org/CVERecord?id=CVE-2026-46080 Référence CVE CVE-2026-46081 https://www.cve.org/CVERecord?id=CVE-2026-46081 Référence CVE CVE-2026-46082 https://www.cve.org/CVERecord?id=CVE-2026-46082 Référence CVE CVE-2026-46083 https://www.cve.org/CVERecord?id=CVE-2026-46083 Référence CVE CVE-2026-46084 https://www.cve.org/CVERecord?id=CVE-2026-46084 Référence CVE CVE-2026-46085 https://www.cve.org/CVERecord?id=CVE-2026-46085 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46087 https://www.cve.org/CVERecord?id=CVE-2026-46087 Référence CVE CVE-2026-46088 https://www.cve.org/CVERecord?id=CVE-2026-46088 Référence CVE CVE-2026-46089 https://www.cve.org/CVERecord?id=CVE-2026-46089 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 Référence CVE CVE-2026-46092 https://www.cve.org/CVERecord?id=CVE-2026-46092 Référence CVE CVE-2026-46093 https://www.cve.org/CVERecord?id=CVE-2026-46093 Référence CVE CVE-2026-46094 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46068 Référence CVE CVE-2026-46069 https://www.cve.org/CVERecord?id=CVE-2026-46069 Référence CVE CVE-2026-46071 https://www.cve.org/CVERecord?id=CVE-2026-46071 Référence CVE CVE-2026-46075 https://www.cve.org/CVERecord?id=CVE-2026-46075 Référence CVE CVE-2026-46076 https://www.cve.org/CVERecord?id=CVE-2026-46076 Référence CVE CVE-2026-46077 https://www.cve.org/CVERecord?id=CVE-2026-46077 Référence CVE CVE-2026-46078 https://www.cve.org/CVERecord?id=CVE-2026-46078 Référence CVE CVE-2026-46079 https://www.cve.org/CVERecord?id=CVE-2026-46079 Référence CVE CVE-2026-46082 https://www.cve.org/CVERecord?id=CVE-2026-46082 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46088 https://www.cve.org/CVERecord?id=CVE-2026-46088 Référence CVE CVE-2026-46089 https://www.cve.org/CVERecord?id=CVE-2026-46089 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 Référence CVE CVE-2026-46092 https://www.cve.org/CVERecord?id=CVE-2026-46092 Référence CVE CVE-2026-46093 https://www.cve.org/CVERecord?id=CVE-2026-46093 Référence CVE CVE-2026-46099 https://www.cve.org/CVERecord?id=CVE-2026-46099 Référence CVE CVE-2026-46101 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-46077 Référence CVE CVE-2026-46078 https://www.cve.org/CVERecord?id=CVE-2026-46078 Référence CVE CVE-2026-46079 https://www.cve.org/CVERecord?id=CVE-2026-46079 Référence CVE CVE-2026-46080 https://www.cve.org/CVERecord?id=CVE-2026-46080 Référence CVE CVE-2026-46081 https://www.cve.org/CVERecord?id=CVE-2026-46081 Référence CVE CVE-2026-46082 https://www.cve.org/CVERecord?id=CVE-2026-46082 Référence CVE CVE-2026-46083 https://www.cve.org/CVERecord?id=CVE-2026-46083 Référence CVE CVE-2026-46084 https://www.cve.org/CVERecord?id=CVE-2026-46084 Référence CVE CVE-2026-46085 https://www.cve.org/CVERecord?id=CVE-2026-46085 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46087 https://www.cve.org/CVERecord?id=CVE-2026-46087 Référence CVE CVE-2026-46088 https://www.cve.org/CVERecord?id=CVE-2026-46088 Référence CVE CVE-2026-46089 https://www.cve.org/CVERecord?id=CVE-2026-46089 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 Référence CVE CVE-2026-46092 https://www.cve.org/CVERecord?id=CVE-2026-46092 Référence CVE CVE-2026-46093 https://www.cve.org/CVERecord?id=CVE-2026-46093 Référence CVE CVE-2026-46094 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31613 Référence CVE CVE-2026-31684 https://www.cve.org/CVERecord?id=CVE-2026-31684 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43330 https://www.cve.org/CVERecord?id=CVE-2026-43330 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46152 https://www.cve.org/CVERecord?id=CVE-2026-46152 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46070 Référence CVE CVE-2026-46072 https://www.cve.org/CVERecord?id=CVE-2026-46072 Référence CVE CVE-2026-46075 https://www.cve.org/CVERecord?id=CVE-2026-46075 Référence CVE CVE-2026-46077 https://www.cve.org/CVERecord?id=CVE-2026-46077 Référence CVE CVE-2026-46078 https://www.cve.org/CVERecord?id=CVE-2026-46078 Référence CVE CVE-2026-46079 https://www.cve.org/CVERecord?id=CVE-2026-46079 Référence CVE CVE-2026-46080 https://www.cve.org/CVERecord?id=CVE-2026-46080 Référence CVE CVE-2026-46082 https://www.cve.org/CVERecord?id=CVE-2026-46082 Référence CVE CVE-2026-46083 https://www.cve.org/CVERecord?id=CVE-2026-46083 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46088 https://www.cve.org/CVERecord?id=CVE-2026-46088 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 Référence CVE CVE-2026-46098 https://www.cve.org/CVERecord?id=CVE-2026-46098 Référence CVE CVE-2026-46099 https://www.cve.org/CVERecord?id=CVE-2026-46099 Référence CVE CVE-2026-46101 https://www.cve.org/CVERecord?id=CVE-2026-46101 Référence CVE CVE-2026-46102 https://www.cve.org/CVERecord?id=CVE-2026-46102 Référence CVE CVE-2026-46103 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46077 Référence CVE CVE-2026-46078 https://www.cve.org/CVERecord?id=CVE-2026-46078 Référence CVE CVE-2026-46079 https://www.cve.org/CVERecord?id=CVE-2026-46079 Référence CVE CVE-2026-46080 https://www.cve.org/CVERecord?id=CVE-2026-46080 Référence CVE CVE-2026-46081 https://www.cve.org/CVERecord?id=CVE-2026-46081 Référence CVE CVE-2026-46082 https://www.cve.org/CVERecord?id=CVE-2026-46082 Référence CVE CVE-2026-46083 https://www.cve.org/CVERecord?id=CVE-2026-46083 Référence CVE CVE-2026-46084 https://www.cve.org/CVERecord?id=CVE-2026-46084 Référence CVE CVE-2026-46085 https://www.cve.org/CVERecord?id=CVE-2026-46085 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46087 https://www.cve.org/CVERecord?id=CVE-2026-46087 Référence CVE CVE-2026-46088 https://www.cve.org/CVERecord?id=CVE-2026-46088 Référence CVE CVE-2026-46089 https://www.cve.org/CVERecord?id=CVE-2026-46089 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 Référence CVE CVE-2026-46092 https://www.cve.org/CVERecord?id=CVE-2026-46092 Référence CVE CVE-2026-46093 https://www.cve.org/CVERecord?id=CVE-2026-46093 Référence CVE CVE-2026-46094 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46077 Référence CVE CVE-2026-46078 https://www.cve.org/CVERecord?id=CVE-2026-46078 Référence CVE CVE-2026-46079 https://www.cve.org/CVERecord?id=CVE-2026-46079 Référence CVE CVE-2026-46080 https://www.cve.org/CVERecord?id=CVE-2026-46080 Référence CVE CVE-2026-46081 https://www.cve.org/CVERecord?id=CVE-2026-46081 Référence CVE CVE-2026-46082 https://www.cve.org/CVERecord?id=CVE-2026-46082 Référence CVE CVE-2026-46083 https://www.cve.org/CVERecord?id=CVE-2026-46083 Référence CVE CVE-2026-46084 https://www.cve.org/CVERecord?id=CVE-2026-46084 Référence CVE CVE-2026-46085 https://www.cve.org/CVERecord?id=CVE-2026-46085 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46087 https://www.cve.org/CVERecord?id=CVE-2026-46087 Référence CVE CVE-2026-46088 https://www.cve.org/CVERecord?id=CVE-2026-46088 Référence CVE CVE-2026-46089 https://www.cve.org/CVERecord?id=CVE-2026-46089 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 Référence CVE CVE-2026-46092 https://www.cve.org/CVERecord?id=CVE-2026-46092 Référence CVE CVE-2026-46093 https://www.cve.org/CVERecord?id=CVE-2026-46093 Référence CVE CVE-2026-46094 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0731Multiples vulnérabilités dans les produits Microsoft

mai 2026 Bulletin de sécurité Microsoft CVE-2026-46072 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46075 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46077 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46078 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46079 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46080 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46082 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46083 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46084 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46085 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46086 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46088 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46089 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46091 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46094 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46098 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46099 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46101 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46102 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46103 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-42496 du 29 mai 2026 Bulletin de sécurité Mic

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: < 3.14, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.86 ≤ 6.12.*, 6.18.27 ≤ 6.18.*, 7.0.4 ≤ 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 27 May 2026 · Last source change 8 Sept 2026, 08:49 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-32469
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enrichment underway

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    960b589f86c74ce582922fcb996103271081f4de < c502fa9f094cb03d1d1685c71e2105ab359bc2b8; 960b589f86c74ce582922fcb996103271081f4de < a6ae4511c07b91f597e461406c6330f0d4ff810e; 960b589f86c74ce582922fcb996103271081f4de < 1406c4e0ed1eaf8a29801ab1163d00fb7ee4359a; 960b589f86c74ce582922fcb996103271081f4de < 0b9e4bbfb7c949151e3acd44ed4aa33614d2e110; 960b589f86c74ce582922fcb996103271081f4de < 81af4137a30c4c2dc694dea8cacb180bd66000ef; 960b589f86c74ce582922fcb996103271081f4de < 5424e678f9b304e148cf5dcc047cffc7a56a3bb5; 960b589f86c74ce582922fcb996103271081f4de < 9a2d9d4e657b23dc21f24cf139e3aeff0b61341f; 960b589f86c74ce582922fcb996103271081f4de < df4601653201de21b487c3e7fffd464790cab808 · Fixed: < 3.14; 5.10.259 ≤ 5.10.*; 5.15.210 ≤ 5.15.*; 6.1.176 ≤ 6.1.*; 6.6.140 ≤ 6.6.*; 6.12.86 ≤ 6.12.*; 6.18.27 ≤ 6.18.*; 7.0.4 ≤ 7.0.*
    After
    Linux: 960b589f86c74ce582922fcb996103271081f4de < c502fa9f094cb03d1d1685c71e2105ab359bc2b8, 960b589f86c74ce582922fcb996103271081f4de < a6ae4511c07b91f597e461406c6330f0d4ff810e, 960b589f86c74ce582922fcb996103271081f4de < 1406c4e0ed1eaf8a29801ab1163d00fb7ee4359a, 960b589f86c74ce582922fcb996103271081f4de < 0b9e4bbfb7c949151e3acd44ed4aa33614d2e110, 960b589f86c74ce582922fcb996103271081f4de < 81af4137a30c4c2dc694dea8cacb180bd66000ef, 960b589f86c74ce582922fcb996103271081f4de < 5424e678f9b304e148cf5dcc047cffc7a56a3bb5, 960b589f86c74ce582922fcb996103271081f4de < 9a2d9d4e657b23dc21f24cf139e3aeff0b61341f, 960b589f86c74ce582922fcb996103271081f4de < df4601653201de21b487c3e7fffd464790cab808, 3.14 · Fixed: Linux: < 3.14, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.86 ≤ 6.12.*, 6.18.27 ≤ 6.18.*, 7.0.4 ≤ 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-32469↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-46086 · cve.blacktree.nl