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

smb: client: validate dacloffset before building DACL pointers

Linux · Linux

9.8CriticalCVSS 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.68% 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 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.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.7-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-46195 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-46195
305 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: smb: client: validate dacloffset before building DACL pointers parse_sec_desc(), build_sec_desc(), and the chown path in id_mode_to_cifs_acl() all add the server-supplied dacloffset to pntsd before proving a DACL header fits inside the returned security descriptor. On 32-bit builds a malicious server can return dacloffset near U32_MAX, wrap the derived DACL pointer below end_of_acl, and then slip past the later pointer-based bounds checks. build_sec_desc() and id_mode_to_cifs_acl() can then dereference DACL fields from the wrapped pointer in the chmod/chown rewrite paths. Validate dacloffset numerically before building any DACL pointer and reuse the same helper at the three DACL entry points.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-46195 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: smb: client: validate dacloffset before building DACL pointers
98 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's Server Message Block (SMB) client. A malicious server can exploit this vulnerability on 32-bit systems by providing a crafted dacloffset value. This can cause a pointer wrap, leading to the dereferencing of invalid Discretionary Access Control List (DACL) fields during chmod or chown operations. This memory corruption could potentially allow the malicious server to bypass security mechanisms or cause a denial of service.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-32822

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate dacloffset before building DACL pointers parse_sec_desc(), build_sec_desc(), and the chown path in id_mode_to_cifs_acl() all add the server-supplied dacloffset to pntsd before proving a DACL header fits inside the returned security descriptor. On 32-bit builds a malicious server can return dacloffset near U32_MAX, wrap the derived DACL pointer below end_of_acl, and then slip past the later pointer-based bounds checks. build_sec_desc() and id_mode_to_cifs_acl() can then dereference DACL fields from the wrapped pointer in the chmod/chown rewrite paths. Validate dacloffset numerically before building any DACL pointer and reuse the same helper at the three DACL entry points.

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
9.8 · CVSS 3.1
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: smb: client: validate dacloffset before building DACL pointers parse_sec_desc(), build_sec_desc(), and the chown path in id_mode_to_cifs_acl() all add the server-supplied dacloffset to pntsd before proving a DACL header fits inside the returned security descriptor. On 32-bit builds a malicious server can return dacloffset near U32_MAX, wrap the derived DACL pointer below end_of_acl, and then slip past the later pointer-based bounds checks. build_sec_desc() and id_mode_to_cifs_acl() can then dereference DACL fields from the wrapped pointer in the chmod/chown rewrite paths. Validate dacloffset numerically before building any DACL pointer and reuse the same helper at the three DACL entry points.

What

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate dacloffset before building DACL pointers parse_sec_desc(), build_sec_desc(), and the chown path in id_mode_to_cifs_acl() all add the server-supplied dacloffset to pntsd before proving a DACL header fits inside the returned security descriptor. On 32-bit builds a malicious server can return dacloffset near U32_MAX, wrap the derived DACL pointer below end_of_acl, and then slip past the later pointer-based bounds checks. build_sec_desc() and id_mode_to_cifs_acl() can then dereference DACL fields from the wrapped pointer in the chmod/chown rewrite paths. Validate dacloffset numerically before building any DACL pointer and reuse the same helper at the three DACL entry points.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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: smb: client: validate dacloffset before building DACL pointers parse_sec_desc(), build_sec_desc(), and the chown path in id_mode_to_cifs_acl() all add the server-supplied dacloffset to pntsd before proving a DACL header fits inside the returned security descriptor. On 32-bit builds a malicious server can return dacloffset near U32_MAX, wrap the derived DACL pointer below end_of_acl, and then slip past the later pointer-based bounds checks. build_sec_desc() and id_mode_to_cifs_acl() can then dereference DACL fields from the wrapped pointer in the chmod/chown rewrite paths. Validate dacloffset numerically before building any DACL pointer and reuse the same helper at the three DACL entry points.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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 Write → 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-787 ↗

CWE-787: Out-of-bounds Write. The product writes 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:H/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.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
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-787
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-32822Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate dacloffset before building DACL pointers parse_sec_desc(), build_sec_desc(), and the chown path in id_mode_to_cifs_acl() all add the server-supplied dacloffset to pntsd before proving a DACL header fits inside the returned security descriptor. On 32-bit builds a malicious server can return dacloffset near U32_MAX, wrap the derived DACL pointer below end_of_acl, and then slip past the later pointer-based bounds checks. build_sec_desc() and id_mode_to_cifs_acl() can then dereference DACL fields from the wrapped pointer in the chmod/chown rewrite paths. Validate dacloffset numerically before building any DACL pointer and reuse the same helper at the three DACL entry points.

Official EUVD record ↗
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-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46188 https://www.cve.org/CVERecord?id=CVE-2026-46188 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46192 https://www.cve.org/CVERecord?id=CVE-2026-46192 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46196 https://www.cve.org/CVERecord?id=CVE-2026-46196 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46199 https://www.cve.org/CVERecord?id=CVE-2026-46199 Référence CVE CVE-2026-46200 https://www.cve.org/CVERecord?id=CVE-2026-46200 Référence CVE CVE-2026-46201 https://www.cve.org/CVERecord?id=CVE-2026-46201 Référence CVE CVE-2026-46202 https://www.cve.org/CVERecord?id=CVE-2026-46202 Référence CVE CVE-2026-46203 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45968 Référence CVE CVE-2026-46007 https://www.cve.org/CVERecord?id=CVE-2026-46007 Référence CVE CVE-2026-46070 https://www.cve.org/CVERecord?id=CVE-2026-46070 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 Référence CVE CVE-2026-46107 https://www.cve.org/CVERecord?id=CVE-2026-46107 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 Référence CVE CVE-2026-46133 https://www.cve.org/CVERecord?id=CVE-2026-46133 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-52912 https://www.cve.org/CVERecord?id=CVE-2026-52912 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52928 https://www.cve.org/CVERecord?id=CVE-2026-52928 Référence CVE CVE-2026-52929 https://www.cve.org/CVERecord?id=CVE-2026-52929 Référence CVE CVE-2026-52935 https://www.cve.org/CVERecord?id=CVE-2026-52935 Référence CVE CVE-2026-52939 https://www.cve.org/CVERecord?id=CVE-2026-52939 Référence CVE CVE-2026-52946 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-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46188 https://www.cve.org/CVERecord?id=CVE-2026-46188 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46192 https://www.cve.org/CVERecord?id=CVE-2026-46192 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46196 https://www.cve.org/CVERecord?id=CVE-2026-46196 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46199 https://www.cve.org/CVERecord?id=CVE-2026-46199 Référence CVE CVE-2026-46200 https://www.cve.org/CVERecord?id=CVE-2026-46200 Référence CVE CVE-2026-46201 https://www.cve.org/CVERecord?id=CVE-2026-46201 Référence CVE CVE-2026-46202 https://www.cve.org/CVERecord?id=CVE-2026-46202 Référence CVE CVE-2026-46203 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46037 Référence CVE CVE-2026-46070 https://www.cve.org/CVERecord?id=CVE-2026-46070 Référence CVE CVE-2026-46078 https://www.cve.org/CVERecord?id=CVE-2026-46078 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 Référence CVE CVE-2026-46107 https://www.cve.org/CVERecord?id=CVE-2026-46107 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-46127 https://www.cve.org/CVERecord?id=CVE-2026-46127 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52929 https://www.cve.org/CVERecord?id=CVE-2026-52929 Référence CVE CVE-2026-52935 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-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46188 https://www.cve.org/CVERecord?id=CVE-2026-46188 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46192 https://www.cve.org/CVERecord?id=CVE-2026-46192 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46196 https://www.cve.org/CVERecord?id=CVE-2026-46196 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46199 https://www.cve.org/CVERecord?id=CVE-2026-46199 Référence CVE CVE-2026-46200 https://www.cve.org/CVERecord?id=CVE-2026-46200 Référence CVE CVE-2026-46201 https://www.cve.org/CVERecord?id=CVE-2026-46201 Référence CVE CVE-2026-46202 https://www.cve.org/CVERecord?id=CVE-2026-46202 Référence CVE CVE-2026-46203 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45897 Référence CVE CVE-2026-45968 https://www.cve.org/CVERecord?id=CVE-2026-45968 Référence CVE CVE-2026-46037 https://www.cve.org/CVERecord?id=CVE-2026-46037 Référence CVE CVE-2026-46070 https://www.cve.org/CVERecord?id=CVE-2026-46070 Référence CVE CVE-2026-46078 https://www.cve.org/CVERecord?id=CVE-2026-46078 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 Référence CVE CVE-2026-46107 https://www.cve.org/CVERecord?id=CVE-2026-46107 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 Référence CVE CVE-2026-46127 https://www.cve.org/CVERecord?id=CVE-2026-46127 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52929 https://www.cve.org/CVERecord?id=CVE-2026-52929 Référence CVE CVE-2026-52935 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-46172 Référence CVE CVE-2026-46174 https://www.cve.org/CVERecord?id=CVE-2026-46174 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46205 https://www.cve.org/CVERecord?id=CVE-2026-46205 Référence CVE CVE-2026-46206 https://www.cve.org/CVERecord?id=CVE-2026-46206 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46212 https://www.cve.org/CVERecord?id=CVE-2026-46212 Référence CVE CVE-2026-46214 https://www.cve.org/CVERecord?id=CVE-2026-46214 Référence CVE CVE-2026-46219 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-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46188 https://www.cve.org/CVERecord?id=CVE-2026-46188 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46192 https://www.cve.org/CVERecord?id=CVE-2026-46192 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46194 https://www.cve.org/CVERecord?id=CVE-2026-46194 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46196 https://www.cve.org/CVERecord?id=CVE-2026-46196 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46199 https://www.cve.org/CVERecord?id=CVE-2026-46199 Référence CVE CVE-2026-46200 https://www.cve.org/CVERecord?id=CVE-2026-46200 Référence CVE CVE-2026-46201 https://www.cve.org/CVERecord?id=CVE-2026-46201 Référence CVE CVE-2026-46202 https://www.cve.org/CVERecord?id=CVE-2026-46202 Référence CVE CVE-2026-46203 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-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46188 https://www.cve.org/CVERecord?id=CVE-2026-46188 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46192 https://www.cve.org/CVERecord?id=CVE-2026-46192 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46194 https://www.cve.org/CVERecord?id=CVE-2026-46194 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46196 https://www.cve.org/CVERecord?id=CVE-2026-46196 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46199 https://www.cve.org/CVERecord?id=CVE-2026-46199 Référence CVE CVE-2026-46200 https://www.cve.org/CVERecord?id=CVE-2026-46200 Référence CVE CVE-2026-46201 https://www.cve.org/CVERecord?id=CVE-2026-46201 Référence CVE CVE-2026-46202 https://www.cve.org/CVERecord?id=CVE-2026-46202 Référence CVE CVE-2026-46203 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-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=CVE-2026-46316 Référence CVE CVE-2026-46325 https://www.cve.org/CVERecord?id=CVE-2026-46325 Gestion détaillée du document le 17 juillet 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales

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

d?id=CVE-2026-46180 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46196 https://www.cve.org/CVERecord?id=CVE-2026-46196 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46199 https://www.cve.org/CVERecord?id=CVE-2026-46199 Référence CVE CVE-2026-46205 https://www.cve.org/CVERecord?id=CVE-2026-46205 Référence CVE CVE-2026-46206 https://www.cve.org/CVERecord?id=CVE-2026-46206 Référence CVE CVE-2026-46208 https://www.cve.org/CVERecord?id=CVE-2026-46208 Référence CVE CVE-2026-46209 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-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=CVE-2026-46246 Référence CVE CVE-2026-46247 https://www.cve.org/CVERecord?id=CVE-2026-46247 Référence CVE CVE-2026-46249 https://www.cve.org/CVERecord?id=CVE-2026-46249 Référence CVE CVE-2026-46250 https://www.cve.org/CVERecord?id=CVE-2026-46250 Référence CVE CVE-2026-46251 https://www.cve.org/CVERecord?id=CVE-2026-46251 Référence CVE CVE-2026-46253 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-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=CVE-2026-46246 Référence CVE CVE-2026-46247 https://www.cve.org/CVERecord?id=CVE-2026-46247 Référence CVE CVE-2026-46249 https://www.cve.org/CVERecord?id=CVE-2026-46249 Référence CVE CVE-2026-46250 https://www.cve.org/CVERecord?id=CVE-2026-46250 Référence CVE CVE-2026-46251 https://www.cve.org/CVERecord?id=CVE-2026-46251 Référence CVE CVE-2026-46253 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-46177 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46178 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46180 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46185 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46186 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46187 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46189 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46190 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46191 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46193 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46195 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46196 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46197 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46198 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46199 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46204 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46205 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46206 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46208 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46209 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46212 du 29 mai 2026 Bulletin de sécurité Mic

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-019316LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。smbクライアントがDACLポインタを構築する前にdacloffsetを検証しなかった問題です。parse_sec_desc()、build_sec_desc()、およびid_mode_to_cifs_acl()のchown経路はすべて、サーバーから提供されたdacloffsetをpntsdに加え、その後返されたセキュリティディスクリプタ内にDACLヘッダーが収まっていることを確認します。32ビットビルドでは、不正なサーバーがdacloffsetを非常に大きな値に設定し、導出されたDACLポインタが境界を越えてラップアラウンドし、その後のポインタベースの境界チェックを回避する可能性がありました。build_sec_desc()およびid_mode_to_cifs_acl()は、その後、chmod/chown書き換え経路においてラップされたポインタからDACLフィールドを間接参照してしまいます。dacloffsetはDACLポインタを構築する前に数値的に検証されるべきであり、同じヘルパー関数を3か所のDACLエントリポイントで使い回す必要があります。

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: < 5.12, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 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 11 Sept 2026, 12:09 UTC · CWE-787 · Out-of-bounds Write

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-32822
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceOther authority
NVD statusNVD modified after enrichment

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
    bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < 5de2665e913a10ad70aaeecf736b97276e83d995; bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < f9dc3be8f403c1216df73e57221f44b045e7ee0b; bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < ba7f71b6161c0943dafc367565e5843d16b7d505; bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < 3b1ddba19e77ee35241cd27f16dc3e8d14e08db7; bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < c688f3ed73d31943334ad2139cb02ec49664322a; bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < 8bd07e417b6bda67e317920584e48cb6ee442a8a; bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < f98b48151cc502ada59d9778f0112d21f2586ca3; 5.12 · Fixed: < 5.12; 5.15.210 ≤ 5.15.*; 6.1.176 ≤ 6.1.*; 6.6.140 ≤ 6.6.*; 6.12.88 ≤ 6.12.*; 6.18.30 ≤ 6.18.*; 7.0.7 ≤ 7.0.*; 7.1 ≤ *
    After
    Linux: bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < 5de2665e913a10ad70aaeecf736b97276e83d995, bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < f9dc3be8f403c1216df73e57221f44b045e7ee0b, bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < ba7f71b6161c0943dafc367565e5843d16b7d505, bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < 3b1ddba19e77ee35241cd27f16dc3e8d14e08db7, bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < c688f3ed73d31943334ad2139cb02ec49664322a, bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < 8bd07e417b6bda67e317920584e48cb6ee442a8a, bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 < f98b48151cc502ada59d9778f0112d21f2586ca3, 5.12 · Fixed: Linux: < 5.12, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.88 ≤ 6.12.*, 6.18.30 ≤ 6.18.*, 7.0.7 ≤ 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-32822↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-46195 · cve.blacktree.nl