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

libceph: Fix slab-out-of-bounds access in auth message processing

Linux · Linux

9.1CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 20 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 severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.72% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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 3 daysRemediation target: Within 90 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 20 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.88-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.7-1Debian Security Tracker ↗Source updated 5 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.

1 current
CVE-2026-46119 · CSAF 2.0 · revision 20 · interimSUSE Product Security TeamCVE-2026-46119
151 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 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: libceph: Fix slab-out-of-bounds access in auth message processing If a (potentially corrupted) message of type CEPH_MSG_AUTH_REPLY contains a positive value in its result field, it is treated as an error code by ceph_handle_auth_reply() and returned to handle_auth_reply(). Thereafter, an attempt is made to send the preallocated message of type CEPH_MSG_AUTH, where the returned value is interpreted as the size of the front segment to send. If the result value in the message is greater than the size of the memory buffer allocated for the front segment, an out-of-bounds access occurs, and the content of the memory region beyond this buffer is sent out. This patch fixes the issue by treating only negative values in the result field as errors. Positive values are therefore treated as success in the same way as a zero value. Additionally, a BUG_ON is added to __send_prepared_auth_request() comparing the len parameter to front_alloc_len to prevent sending the message if it exceeds the bounds of the allocation and to make it easier to catch any logic flaws leading to this.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-32878

No EUVD known-exploited evidence

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

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

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 20 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: libceph: Fix slab-out-of-bounds access in auth message processing If a (potentially corrupted) message of type CEPH_MSG_AUTH_REPLY contains a positive value in its result field, it is treated as an error code by ceph_handle_auth_reply() and returned to handle_auth_reply(). Thereafter, an attempt is made to send the preallocated message of type CEPH_MSG_AUTH, where the returned value is interpreted as the size of the front segment to send. If the result value in the message is greater than the size of the memory buffer allocated for the front segment, an out-of-bounds access occurs, and the content of the memory region beyond this buffer is sent out. This patch fixes the issue by treating only negative values in the result field as errors. Positive values are therefore treated as success in the same way as a zero value. Additionally, a BUG_ON is added to __send_prepared_auth_request() comparing the len parameter to front_alloc_len to prevent sending the message if it exceeds the bounds of the allocation and to make it easier to catch any logic flaws leading to this.

What

In the Linux kernel, the following vulnerability has been resolved: libceph: Fix slab-out-of-bounds access in auth message processing If a (potentially corrupted) message of type CEPH_MSG_AUTH_REPLY contains a positive value in its result field, it is treated as an error code by ceph_handle_auth_reply() and returned to handle_auth_reply(). Thereafter, an attempt is made to send the preallocated message of type CEPH_MSG_AUTH, where the returned value is interpreted as the size of the front segment to send. If the result value in the message is greater than the size of the memory buffer allocated for the front segment, an out-of-bounds access occurs, and the content of the memory region beyond this buffer is sent out. This patch fixes the issue by treating only negative values in the result field as errors. Positive values are therefore treated as success in the same way as a zero value. Additionally, a BUG_ON is added to __send_prepared_auth_request() comparing the len parameter to front_alloc_len to prevent sending the message if it exceeds the bounds of the allocation and to make it easier to catch any logic flaws leading to this.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path 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: libceph: Fix slab-out-of-bounds access in auth message processing If a (potentially corrupted) message of type CEPH_MSG_AUTH_REPLY contains a positive value in its result field, it is treated as an error code by ceph_handle_auth_reply() and returned to handle_auth_reply(). Thereafter, an attempt is made to send the preallocated message of type CEPH_MSG_AUTH, where the returned value is interpreted as the size of the front segment to send. If the result value in the message is greater than the size of the memory buffer allocated for the front segment, an out-of-bounds access occurs, and the content of the memory region beyond this buffer is sent out. This patch fixes the issue by treating only negative values in the result field as errors. Positive values are therefore treated as success in the same way as a zero value. Additionally, a BUG_ON is added to __send_prepared_auth_request() comparing the len parameter to front_alloc_len to prevent sending the message if it exceeds the bounds of the allocation and to make it easier to catch any logic flaws leading to this.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path 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
a network path → Out-of-bounds Read → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

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

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.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.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-125
A

Official authority intelligence

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

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-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46110 Référence CVE CVE-2026-46111 https://www.cve.org/CVERecord?id=CVE-2026-46111 Référence CVE CVE-2026-46112 https://www.cve.org/CVERecord?id=CVE-2026-46112 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46114 https://www.cve.org/CVERecord?id=CVE-2026-46114 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 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-46118 https://www.cve.org/CVERecord?id=CVE-2026-46118 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46121 https://www.cve.org/CVERecord?id=CVE-2026-46121 Référence CVE CVE-2026-46122 https://www.cve.org/CVERecord?id=CVE-2026-46122 Référence CVE CVE-2026-46123 https://www.cve.org/CVERecord?id=CVE-2026-46123 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46125 https://www.cve.org/CVERecord?id=CVE-2026-46125 Référence CVE CVE-2026-46126 https://www.cve.org/CVERecord?id=CVE-2026-46126 Référence CVE CVE-2026-46127 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-46110 Référence CVE CVE-2026-46111 https://www.cve.org/CVERecord?id=CVE-2026-46111 Référence CVE CVE-2026-46112 https://www.cve.org/CVERecord?id=CVE-2026-46112 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46114 https://www.cve.org/CVERecord?id=CVE-2026-46114 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 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-46118 https://www.cve.org/CVERecord?id=CVE-2026-46118 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46121 https://www.cve.org/CVERecord?id=CVE-2026-46121 Référence CVE CVE-2026-46122 https://www.cve.org/CVERecord?id=CVE-2026-46122 Référence CVE CVE-2026-46123 https://www.cve.org/CVERecord?id=CVE-2026-46123 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46125 https://www.cve.org/CVERecord?id=CVE-2026-46125 Référence CVE CVE-2026-46126 https://www.cve.org/CVERecord?id=CVE-2026-46126 Référence CVE CVE-2026-46127 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46110 Référence CVE CVE-2026-46111 https://www.cve.org/CVERecord?id=CVE-2026-46111 Référence CVE CVE-2026-46112 https://www.cve.org/CVERecord?id=CVE-2026-46112 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46114 https://www.cve.org/CVERecord?id=CVE-2026-46114 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 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-46118 https://www.cve.org/CVERecord?id=CVE-2026-46118 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46121 https://www.cve.org/CVERecord?id=CVE-2026-46121 Référence CVE CVE-2026-46122 https://www.cve.org/CVERecord?id=CVE-2026-46122 Référence CVE CVE-2026-46123 https://www.cve.org/CVERecord?id=CVE-2026-46123 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46125 https://www.cve.org/CVERecord?id=CVE-2026-46125 Référence CVE CVE-2026-46126 https://www.cve.org/CVERecord?id=CVE-2026-46126 Référence CVE CVE-2026-46127 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46088 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-46107 https://www.cve.org/CVERecord?id=CVE-2026-46107 Référence CVE CVE-2026-46108 https://www.cve.org/CVERecord?id=CVE-2026-46108 Référence CVE CVE-2026-46112 https://www.cve.org/CVERecord?id=CVE-2026-46112 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46122 https://www.cve.org/CVERecord?id=CVE-2026-46122 Référence CVE CVE-2026-46123 https://www.cve.org/CVERecord?id=CVE-2026-46123 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46127 https://www.cve.org/CVERecord?id=CVE-2026-46127 Référence CVE CVE-2026-46128 https://www.cve.org/CVERecord?id=CVE-2026-46128 Référence CVE CVE-2026-46132 https://www.cve.org/CVERecord?id=CVE-2026-46132 Référence CVE CVE-2026-46133 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43407 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43465 https://www.cve.org/CVERecord?id=CVE-2026-43465 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45988 https://www.cve.org/CVERecord?id=CVE-2026-45988 Référence CVE CVE-2026-46043 https://www.cve.org/CVERecord?id=CVE-2026-46043 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46137 https://www.cve.org/CVERecord?id=CVE-2026-46137 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46325 https://www.cve.org/CVERecord?id=CVE-2026-46325 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52914 https://www.cve.org/CVERecord?id=CVE-2026-52914 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46079 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 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=CVE-2026-46101 Référence CVE CVE-2026-46111 https://www.cve.org/CVERecord?id=CVE-2026-46111 Référence CVE CVE-2026-46112 https://www.cve.org/CVERecord?id=CVE-2026-46112 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-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46160 https://www.cve.org/CVERecord?id=CVE-2026-46160 Référence CVE CVE-2026-46161 https://www.cve.org/CVERecord?id=CVE-2026-46161 Référence CVE CVE-2026-46162 https://www.cve.org/CVERecord?id=CVE-2026-46162 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 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-46110 Référence CVE CVE-2026-46111 https://www.cve.org/CVERecord?id=CVE-2026-46111 Référence CVE CVE-2026-46112 https://www.cve.org/CVERecord?id=CVE-2026-46112 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46114 https://www.cve.org/CVERecord?id=CVE-2026-46114 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 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-46118 https://www.cve.org/CVERecord?id=CVE-2026-46118 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46121 https://www.cve.org/CVERecord?id=CVE-2026-46121 Référence CVE CVE-2026-46122 https://www.cve.org/CVERecord?id=CVE-2026-46122 Référence CVE CVE-2026-46123 https://www.cve.org/CVERecord?id=CVE-2026-46123 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46125 https://www.cve.org/CVERecord?id=CVE-2026-46125 Référence CVE CVE-2026-46126 https://www.cve.org/CVERecord?id=CVE-2026-46126 Référence CVE CVE-2026-46127 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-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=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=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-46111 https://www.cve.org/CVERecord?id=CVE-2026-46111 Référence CVE CVE-2026-46112 https://www.cve.org/CVERecord?id=CVE-2026-46112 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46122 https://www.cve.org/CVERecord?id=CVE-2026-46122 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46125 https://www.cve.org/CVERecord?id=CVE-2026-46125 Référence CVE CVE-2026-46128 https://www.cve.org/CVERecord?id=CVE-2026-46128 Référence CVE CVE-2026-46131 https://www.cve.org/CVERecord?id=CVE-2026-46131 Référence CVE CVE-2026-46132 https://www.cve.org/CVERecord?id=CVE-2026-46132 Référence CVE CVE-2026-46136 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-46110 Référence CVE CVE-2026-46111 https://www.cve.org/CVERecord?id=CVE-2026-46111 Référence CVE CVE-2026-46112 https://www.cve.org/CVERecord?id=CVE-2026-46112 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46114 https://www.cve.org/CVERecord?id=CVE-2026-46114 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 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-46118 https://www.cve.org/CVERecord?id=CVE-2026-46118 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46121 https://www.cve.org/CVERecord?id=CVE-2026-46121 Référence CVE CVE-2026-46122 https://www.cve.org/CVERecord?id=CVE-2026-46122 Référence CVE CVE-2026-46123 https://www.cve.org/CVERecord?id=CVE-2026-46123 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46125 https://www.cve.org/CVERecord?id=CVE-2026-46125 Référence CVE CVE-2026-46126 https://www.cve.org/CVERecord?id=CVE-2026-46126 Référence CVE CVE-2026-46127 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43414 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45898 https://www.cve.org/CVERecord?id=CVE-2026-45898 Référence CVE CVE-2026-45988 https://www.cve.org/CVERecord?id=CVE-2026-45988 Référence CVE CVE-2026-46039 https://www.cve.org/CVERecord?id=CVE-2026-46039 Référence CVE CVE-2026-46043 https://www.cve.org/CVERecord?id=CVE-2026-46043 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46289 https://www.cve.org/CVERecord?id=CVE-2026-46289 Référence CVE CVE-2026-46316 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46090 Référence CVE CVE-2026-46094 https://www.cve.org/CVERecord?id=CVE-2026-46094 Référence CVE CVE-2026-46101 https://www.cve.org/CVERecord?id=CVE-2026-46101 Référence CVE CVE-2026-46110 https://www.cve.org/CVERecord?id=CVE-2026-46110 Référence CVE CVE-2026-46111 https://www.cve.org/CVERecord?id=CVE-2026-46111 Référence CVE CVE-2026-46112 https://www.cve.org/CVERecord?id=CVE-2026-46112 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46114 https://www.cve.org/CVERecord?id=CVE-2026-46114 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46123 https://www.cve.org/CVERecord?id=CVE-2026-46123 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46133 https://www.cve.org/CVERecord?id=CVE-2026-46133 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46157 https://www.cve.org/CVERecord?id=CVE-2026-46157 Référence CVE CVE-2026-46159 https://www.cve.org/CVERecord?id=CVE-2026-46159 Référence CVE CVE-2026-46160 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-46102 Référence CVE CVE-2026-46103 https://www.cve.org/CVERecord?id=CVE-2026-46103 Référence CVE CVE-2026-46107 https://www.cve.org/CVERecord?id=CVE-2026-46107 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=CVE-2026-46109 Référence CVE CVE-2026-46110 https://www.cve.org/CVERecord?id=CVE-2026-46110 Référence CVE CVE-2026-46112 https://www.cve.org/CVERecord?id=CVE-2026-46112 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-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46122 https://www.cve.org/CVERecord?id=CVE-2026-46122 Référence CVE CVE-2026-46123 https://www.cve.org/CVERecord?id=CVE-2026-46123 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46125 https://www.cve.org/CVERecord?id=CVE-2026-46125 Référence CVE CVE-2026-46127 https://www.cve.org/CVERecord?id=CVE-2026-46127 Référence CVE CVE-2026-46128 https://www.cve.org/CVERecord?id=CVE-2026-46128 Référence CVE CVE-2026-46129 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-46096 Référence CVE CVE-2026-46097 https://www.cve.org/CVERecord?id=CVE-2026-46097 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-46100 https://www.cve.org/CVERecord?id=CVE-2026-46100 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=CVE-2026-46103 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46137 https://www.cve.org/CVERecord?id=CVE-2026-46137 Référence CVE CVE-2026-46155 https://www.cve.org/CVERecord?id=CVE-2026-46155 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46246 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46083 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46094 https://www.cve.org/CVERecord?id=CVE-2026-46094 Référence CVE CVE-2026-46101 https://www.cve.org/CVERecord?id=CVE-2026-46101 Référence CVE CVE-2026-46110 https://www.cve.org/CVERecord?id=CVE-2026-46110 Référence CVE CVE-2026-46111 https://www.cve.org/CVERecord?id=CVE-2026-46111 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46114 https://www.cve.org/CVERecord?id=CVE-2026-46114 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46123 https://www.cve.org/CVERecord?id=CVE-2026-46123 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46157 https://www.cve.org/CVERecord?id=CVE-2026-46157 Référence CVE CVE-2026-46159 https://www.cve.org/CVERecord?id=CVE-2026-46159 Référence CVE CVE-2026-46160 https://www.cve.org/CVERecord?id=CVE-2026-46160 Référence CVE CVE-2026-46162 https://www.cve.org/CVERecord?id=CVE-2026-46162 Référence CVE CVE-2026-46172 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-46096 Référence CVE CVE-2026-46097 https://www.cve.org/CVERecord?id=CVE-2026-46097 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-46100 https://www.cve.org/CVERecord?id=CVE-2026-46100 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=CVE-2026-46103 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46137 https://www.cve.org/CVERecord?id=CVE-2026-46137 Référence CVE CVE-2026-46155 https://www.cve.org/CVERecord?id=CVE-2026-46155 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46246 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-46107 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46108 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46109 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46110 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46111 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46112 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46113 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46114 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46115 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46116 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46119 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46120 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46122 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46123 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46124 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46125 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46127 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46128 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46129 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46131 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46132 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: < 2.6.34, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.88 ≤ 6.12.*, 6.18.30 ≤ 6.18.*, 7.0.7 ≤ 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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 28 May 2026 · Last source change 5 Aug 2026, 12:29 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-32878
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 ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-46119 · cve.blacktree.nl