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

smb: client: require a full NFS mode SID before reading mode bits

Linux · Linux

7.6HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 252 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

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

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 252 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.85-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.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.3-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.

1 current
CVE-2026-43350 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: smb: client: require a full NFS mode SID before reading mode bits
232 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 CIFS/SMB client when parsing DACLs (`parse_dacl`). An ACE could match the Unix NFS mode SID prefix with only two subauthorities; code then read `sub_auth[2]` for mode bits, accessing four bytes past the end of the ACE buffer. Upstream requires `num_subauth >= 3` before treating an ACE as an NFS mode SID.
Remediation
To mitigate this issue, prevent the cifs module from being loaded. See https://access.redhat.com/solutions/41278 for instructions.
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-28634

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 252 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: require a full NFS mode SID before reading mode bits parse_dacl() treats an ACE SID matching sid_unix_NFS_mode as an NFS mode SID and reads sid.sub_auth[2] to recover the mode bits. That assumes the ACE carries three subauthorities, but compare_sids() only compares min(a, b) subauthorities. A malicious server can return an ACE with num_subauth = 2 and sub_auth[] = {88, 3}, which still matches sid_unix_NFS_mode and then drives the sub_auth[2] read four bytes past the end of the ACE. Require num_subauth >= 3 before treating the ACE as an NFS mode SID. This keeps the fix local to the special-SID mode path without changing compare_sids() semantics for the rest of cifsacl.

What

In the Linux kernel, the following vulnerability has been resolved: smb: client: require a full NFS mode SID before reading mode bits parse_dacl() treats an ACE SID matching sid_unix_NFS_mode as an NFS mode SID and reads sid.sub_auth[2] to recover the mode bits. That assumes the ACE carries three subauthorities, but compare_sids() only compares min(a, b) subauthorities. A malicious server can return an ACE with num_subauth = 2 and sub_auth[] = {88, 3}, which still matches sid_unix_NFS_mode and then drives the sub_auth[2] read four bytes past the end of the ACE. Require num_subauth >= 3 before treating the ACE as an NFS mode SID. This keeps the fix local to the special-SID mode path without changing compare_sids() semantics for the rest of cifsacl.

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication after a 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: require a full NFS mode SID before reading mode bits parse_dacl() treats an ACE SID matching sid_unix_NFS_mode as an NFS mode SID and reads sid.sub_auth[2] to recover the mode bits. That assumes the ACE carries three subauthorities, but compare_sids() only compares min(a, b) subauthorities. A malicious server can return an ACE with num_subauth = 2 and sub_auth[] = {88, 3}, which still matches sid_unix_NFS_mode and then drives the sub_auth[2] read four bytes past the end of the ACE. Require num_subauth >= 3 before treating the ACE as an NFS mode SID. This keeps the fix local to the special-SID mode path without changing compare_sids() semantics for the rest of cifsacl.

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication after a 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 → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited 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.
NetworkUnauthenticated
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-1454Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.

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

d?id=CVE-2026-43333 Référence CVE CVE-2026-43334 https://www.cve.org/CVERecord?id=CVE-2026-43334 Référence CVE CVE-2026-43336 https://www.cve.org/CVERecord?id=CVE-2026-43336 Référence CVE CVE-2026-43338 https://www.cve.org/CVERecord?id=CVE-2026-43338 Référence CVE CVE-2026-43339 https://www.cve.org/CVERecord?id=CVE-2026-43339 Référence CVE CVE-2026-43340 https://www.cve.org/CVERecord?id=CVE-2026-43340 Référence CVE CVE-2026-43342 https://www.cve.org/CVERecord?id=CVE-2026-43342 Référence CVE CVE-2026-43343 https://www.cve.org/CVERecord?id=CVE-2026-43343 Référence CVE CVE-2026-43345 https://www.cve.org/CVERecord?id=CVE-2026-43345 Référence CVE CVE-2026-43350 https://www.cve.org/CVERecord?id=CVE-2026-43350 Référence CVE CVE-2026-43355 https://www.cve.org/CVERecord?id=CVE-2026-43355 Référence CVE CVE-2026-43357 https://www.cve.org/CVERecord?id=CVE-2026-43357 Référence CVE CVE-2026-43359 https://www.cve.org/CVERecord?id=CVE-2026-43359 Référence CVE CVE-2026-43360 https://www.cve.org/CVERecord?id=CVE-2026-43360 Référence CVE CVE-2026-43361 https://www.cve.org/CVERecord?id=CVE-2026-43361 Référence CVE CVE-2026-43362 https://www.cve.org/CVERecord?id=CVE-2026-43362 Référence CVE CVE-2026-43363 https://www.cve.org/CVERecord?id=CVE-2026-43363 Référence CVE CVE-2026-43365 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-43338 Référence CVE CVE-2026-43339 https://www.cve.org/CVERecord?id=CVE-2026-43339 Référence CVE CVE-2026-43340 https://www.cve.org/CVERecord?id=CVE-2026-43340 Référence CVE CVE-2026-43341 https://www.cve.org/CVERecord?id=CVE-2026-43341 Référence CVE CVE-2026-43342 https://www.cve.org/CVERecord?id=CVE-2026-43342 Référence CVE CVE-2026-43343 https://www.cve.org/CVERecord?id=CVE-2026-43343 Référence CVE CVE-2026-43345 https://www.cve.org/CVERecord?id=CVE-2026-43345 Référence CVE CVE-2026-43348 https://www.cve.org/CVERecord?id=CVE-2026-43348 Référence CVE CVE-2026-43349 https://www.cve.org/CVERecord?id=CVE-2026-43349 Référence CVE CVE-2026-43350 https://www.cve.org/CVERecord?id=CVE-2026-43350 Référence CVE CVE-2026-43355 https://www.cve.org/CVERecord?id=CVE-2026-43355 Référence CVE CVE-2026-43357 https://www.cve.org/CVERecord?id=CVE-2026-43357 Référence CVE CVE-2026-43359 https://www.cve.org/CVERecord?id=CVE-2026-43359 Référence CVE CVE-2026-43360 https://www.cve.org/CVERecord?id=CVE-2026-43360 Référence CVE CVE-2026-43361 https://www.cve.org/CVERecord?id=CVE-2026-43361 Référence CVE CVE-2026-43362 https://www.cve.org/CVERecord?id=CVE-2026-43362 Référence CVE CVE-2026-43363 https://www.cve.org/CVERecord?id=CVE-2026-43363 Référence CVE CVE-2026-43365 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-43338 Référence CVE CVE-2026-43339 https://www.cve.org/CVERecord?id=CVE-2026-43339 Référence CVE CVE-2026-43340 https://www.cve.org/CVERecord?id=CVE-2026-43340 Référence CVE CVE-2026-43341 https://www.cve.org/CVERecord?id=CVE-2026-43341 Référence CVE CVE-2026-43342 https://www.cve.org/CVERecord?id=CVE-2026-43342 Référence CVE CVE-2026-43343 https://www.cve.org/CVERecord?id=CVE-2026-43343 Référence CVE CVE-2026-43345 https://www.cve.org/CVERecord?id=CVE-2026-43345 Référence CVE CVE-2026-43348 https://www.cve.org/CVERecord?id=CVE-2026-43348 Référence CVE CVE-2026-43349 https://www.cve.org/CVERecord?id=CVE-2026-43349 Référence CVE CVE-2026-43350 https://www.cve.org/CVERecord?id=CVE-2026-43350 Référence CVE CVE-2026-43355 https://www.cve.org/CVERecord?id=CVE-2026-43355 Référence CVE CVE-2026-43357 https://www.cve.org/CVERecord?id=CVE-2026-43357 Référence CVE CVE-2026-43359 https://www.cve.org/CVERecord?id=CVE-2026-43359 Référence CVE CVE-2026-43360 https://www.cve.org/CVERecord?id=CVE-2026-43360 Référence CVE CVE-2026-43361 https://www.cve.org/CVERecord?id=CVE-2026-43361 Référence CVE CVE-2026-43362 https://www.cve.org/CVERecord?id=CVE-2026-43362 Référence CVE CVE-2026-43363 https://www.cve.org/CVERecord?id=CVE-2026-43363 Référence CVE CVE-2026-43365 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-43112 Référence CVE CVE-2026-43113 https://www.cve.org/CVERecord?id=CVE-2026-43113 Référence CVE CVE-2026-43114 https://www.cve.org/CVERecord?id=CVE-2026-43114 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43117 https://www.cve.org/CVERecord?id=CVE-2026-43117 Référence CVE CVE-2026-43216 https://www.cve.org/CVERecord?id=CVE-2026-43216 Référence CVE CVE-2026-43219 https://www.cve.org/CVERecord?id=CVE-2026-43219 Référence CVE CVE-2026-43281 https://www.cve.org/CVERecord?id=CVE-2026-43281 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43350 https://www.cve.org/CVERecord?id=CVE-2026-43350 Référence CVE CVE-2026-43355 https://www.cve.org/CVERecord?id=CVE-2026-43355 Référence CVE CVE-2026-43421 https://www.cve.org/CVERecord?id=CVE-2026-43421 Référence CVE CVE-2026-43492 https://www.cve.org/CVERecord?id=CVE-2026-43492 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 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-43315 Référence CVE CVE-2026-43316 https://www.cve.org/CVERecord?id=CVE-2026-43316 Référence CVE CVE-2026-43317 https://www.cve.org/CVERecord?id=CVE-2026-43317 Référence CVE CVE-2026-43318 https://www.cve.org/CVERecord?id=CVE-2026-43318 Référence CVE CVE-2026-43319 https://www.cve.org/CVERecord?id=CVE-2026-43319 Référence CVE CVE-2026-43320 https://www.cve.org/CVERecord?id=CVE-2026-43320 Référence CVE CVE-2026-43341 https://www.cve.org/CVERecord?id=CVE-2026-43341 Référence CVE CVE-2026-43348 https://www.cve.org/CVERecord?id=CVE-2026-43348 Référence CVE CVE-2026-43349 https://www.cve.org/CVERecord?id=CVE-2026-43349 Référence CVE CVE-2026-43350 https://www.cve.org/CVERecord?id=CVE-2026-43350 Référence CVE CVE-2026-43376 https://www.cve.org/CVERecord?id=CVE-2026-43376 Référence CVE CVE-2026-43378 https://www.cve.org/CVERecord?id=CVE-2026-43378 Référence CVE CVE-2026-43383 https://www.cve.org/CVERecord?id=CVE-2026-43383 Référence CVE CVE-2026-43384 https://www.cve.org/CVERecord?id=CVE-2026-43384 Référence CVE CVE-2026-43402 https://www.cve.org/CVERecord?id=CVE-2026-43402 Référence CVE CVE-2026-43406 https://www.cve.org/CVERecord?id=CVE-2026-43406 Référence CVE CVE-2026-43407 https://www.cve.org/CVERecord?id=CVE-2026-43407 Référence CVE CVE-2026-43414 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-43315 Référence CVE CVE-2026-43316 https://www.cve.org/CVERecord?id=CVE-2026-43316 Référence CVE CVE-2026-43317 https://www.cve.org/CVERecord?id=CVE-2026-43317 Référence CVE CVE-2026-43318 https://www.cve.org/CVERecord?id=CVE-2026-43318 Référence CVE CVE-2026-43319 https://www.cve.org/CVERecord?id=CVE-2026-43319 Référence CVE CVE-2026-43320 https://www.cve.org/CVERecord?id=CVE-2026-43320 Référence CVE CVE-2026-43341 https://www.cve.org/CVERecord?id=CVE-2026-43341 Référence CVE CVE-2026-43348 https://www.cve.org/CVERecord?id=CVE-2026-43348 Référence CVE CVE-2026-43349 https://www.cve.org/CVERecord?id=CVE-2026-43349 Référence CVE CVE-2026-43350 https://www.cve.org/CVERecord?id=CVE-2026-43350 Référence CVE CVE-2026-43376 https://www.cve.org/CVERecord?id=CVE-2026-43376 Référence CVE CVE-2026-43378 https://www.cve.org/CVERecord?id=CVE-2026-43378 Référence CVE CVE-2026-43383 https://www.cve.org/CVERecord?id=CVE-2026-43383 Référence CVE CVE-2026-43384 https://www.cve.org/CVERecord?id=CVE-2026-43384 Référence CVE CVE-2026-43402 https://www.cve.org/CVERecord?id=CVE-2026-43402 Référence CVE CVE-2026-43406 https://www.cve.org/CVERecord?id=CVE-2026-43406 Référence CVE CVE-2026-43407 https://www.cve.org/CVERecord?id=CVE-2026-43407 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-015849LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。smbでは、クライアントがモードビットを読み取る前に完全なNFSモードSIDを要求します。parse_dacl()は、sid_unix_NFS_modeと一致するACE SIDをNFSモードSIDとして扱い、モードビットを復元するためにsid.sub_auth[2]を読み取ります。この処理はACEが3つのサブオーソリティを持つことを前提としていますが、compare_sids()はmin(a, b)のサブオーソリティのみを比較します。悪意のあるサーバーはnum_subauth = 2かつsub_auth[] = {88, 3}のACEを返し、これによりsid_unix_NFS_modeと一致し、sub_auth[2]の読み取りがACEの末尾から4バイト上書きして読み取られる可能性があります。ACEをNFSモードSIDとして扱う前にnum_subauth = 3であることを要求します。これにより特別なSIDモードパスの修正に限定され、cifsaclの他の部分のcompare_sids()の動作には影響を与えません。

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.4, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.136 ≤ 6.6.*, 6.12.84 ≤ 6.12.*, 6.18.25 ≤ 6.18.*, 7.0.2 ≤ 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
To mitigate this issue, prevent the cifs module from being loaded. See https://access.redhat.com/solutions/41278 for instructions.
04

Evidence and provenance

Published 8 May 2026 · Last source change 5 Aug 2026, 12:27 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-28634
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗

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
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-28634↗Vendor CSAF · Red Hat Product Security↗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-43350 · cve.blacktree.nl