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

fhandle: fix UAF due to unlocked ->mnt_ns read in may_decode_fh()

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 13 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.

17 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 13 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.95-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, 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-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-azure-fde-6.14Affected, 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-nvidia-6.14Affected, 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-gcp-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-hwe-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-lowlatency-hwe-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-nvidia-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-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-oracle-6.14Affected, 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
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-53341 · CSAF 2.0 · revision 6 · interimSUSE Product Security TeamCVE-2026-53341
19 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise Server 16.0
  • kernel-devel as component of SUSE Linux Enterprise Server 16.0
  • kernel-macros as component of SUSE Linux Enterprise Server 16.0
  • kernel-source as component of SUSE Linux Enterprise Server 16.0
  • kernel-source-vanilla as component of SUSE Linux Enterprise Server 16.0
  • kernel-default as component of SUSE Linux Enterprise Server for SAP applications 16.0
  • kernel-devel as component of SUSE Linux Enterprise Server for SAP applications 16.0
  • kernel-macros as component of SUSE Linux Enterprise Server for SAP applications 16.0
  • kernel-source as component of SUSE Linux Enterprise Server for SAP applications 16.0
  • kernel-source-vanilla as component of SUSE Linux Enterprise Server for SAP applications 16.0
Summary
In the Linux kernel, the following vulnerability has been resolved: fhandle: fix UAF due to unlocked ->mnt_ns read in may_decode_fh() may_decode_fh() accesses mount::mnt_ns without holding any locks; that means the mount can concurrently be unmounted, and the mnt_namespace can concurrently be freed after an RCU grace period. This race can happens as follows, assuming that the mount point was created by open_tree(..., OPEN_TREE_CLONE): thread 1 thread 2 RCU __do_sys_open_by_handle_at do_handle_open handle_to_path may_decode_fh is_mounted [mount::mnt_ns access] [mount::mnt_ns access] __do_sys_close fput_close_sync __fput dissolve_on_fput umount_tree class_namespace_excl_destructor namespace_unlock free_mnt_ns mnt_ns_tree_remove call_rcu(mnt_ns_release_rcu) mnt_ns_release_rcu mnt_ns_release kfree [mnt_namespace::user_ns access] **UAF** Fix it by taking rcu_read_lock() around the mount::mnt_ns access, like in __prepend_path(). Additionally, document the semantics of mount::mnt_ns, and use WRITE_ONCE() for writers that can race with lockless readers. This bug is unreachable unless one of the following is set: - CONFIG_PREEMPTION - CONFIG_RCU_STRICT_GRACE_PERIOD because it requires an RCU grace period to happen during a syscall without an explicit preemption. This doesn't seem to have interesting security impact; worst-case, it could leak the result of an integer comparison to userspace (from the level check in cap_capable()), cause an endless loop, or crash the kernel by dereferencing an invalid address.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-53341 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: fhandle: fix UAF due to unlocked ->mnt_ns read in may_decode_fh()
36 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel. This vulnerability, a Use-After-Free (UAF), occurs in the `fhandle` component when the `may_decode_fh()` function accesses mount namespace information without proper locking. This creates a race condition that could be exploited by an attacker. The most severe consequence is a kernel crash, leading to a Denial of Service (DoS), but it could also result in an endless loop or the disclosure of sensitive information.
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. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
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-40975

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 13 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: fhandle: fix UAF due to unlocked ->mnt_ns read in may_decode_fh() may_decode_fh() accesses mount::mnt_ns without holding any locks; that means the mount can concurrently be unmounted, and the mnt_namespace can concurrently be freed after an RCU grace period. This race can happens as follows, assuming that the mount point was created by open_tree(..., OPEN_TREE_CLONE): thread 1 thread 2 RCU __do_sys_open_by_handle_at do_handle_open handle_to_path may_decode_fh is_mounted [mount::mnt_ns access] [mount::mnt_ns access] __do_sys_close fput_close_sync __fput dissolve_on_fput umount_tree class_namespace_excl_destructor namespace_unlock free_mnt_ns mnt_ns_tree_remove call_rcu(mnt_ns_release_rcu) mnt_ns_release_rcu mnt_ns_release kfree [mnt_namespace::user_ns access] **UAF** Fix it by taking rcu_read_lock() around the mount::mnt_ns access, like in __prepend_path(). Additionally, document the semantics of mount::mnt_ns, and use WRITE_ONCE() for writers that can race with lockless readers. This bug is unreachable unless one of the following is set: - CONFIG_PREEMPTION - CONFIG_RCU_STRICT_GRACE_PERIOD because it requires an RCU grace period to happen during a syscall without an explicit preemption. This doesn't seem to have interesting security impact; worst-case, it could leak the result of an integer comparison to userspace (from the level check in cap_capable()), cause an endless loop, or crash the kernel by dereferencing an invalid address.

What

In the Linux kernel, the following vulnerability has been resolved: fhandle: fix UAF due to unlocked ->mnt_ns read in may_decode_fh() may_decode_fh() accesses mount::mnt_ns without holding any locks; that means the mount can concurrently be unmounted, and the mnt_namespace can concurrently be freed after an RCU grace period. This race can happens as follows, assuming that the mount point was created by open_tree(..., OPEN_TREE_CLONE): thread 1 thread 2 RCU __do_sys_open_by_handle_at do_handle_open handle_to_path may_decode_fh is_mounted [mount::mnt_ns access] [mount::mnt_ns access] __do_sys_close fput_close_sync __fput dissolve_on_fput umount_tree class_namespace_excl_destructor namespace_unlock free_mnt_ns mnt_ns_tree_remove call_rcu(mnt_ns_release_rcu) mnt_ns_release_rcu mnt_ns_release kfree [mnt_namespace::user_ns access] **UAF** Fix it by taking rcu_read_lock() around the mount::mnt_ns access, like in __prepend_path(). Additionally, document the semantics of mount::mnt_ns, and use WRITE_ONCE() for writers that can race with lockless readers. This bug is unreachable unless one of the following is set: - CONFIG_PREEMPTION - CONFIG_RCU_STRICT_GRACE_PERIOD because it requires an RCU grace period to happen during a syscall without an explicit preemption. This doesn't seem to have interesting security impact; worst-case, it could leak the result of an integer comparison to userspace (from the level check in cap_capable()), cause an endless loop, or crash the kernel by dereferencing an invalid address.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: fhandle: fix UAF due to unlocked ->mnt_ns read in may_decode_fh() may_decode_fh() accesses mount::mnt_ns without holding any locks; that means the mount can concurrently be unmounted, and the mnt_namespace can concurrently be freed after an RCU grace period. This race can happens as follows, assuming that the mount point was created by open_tree(..., OPEN_TREE_CLONE): thread 1 thread 2 RCU __do_sys_open_by_handle_at do_handle_open handle_to_path may_decode_fh is_mounted [mount::mnt_ns access] [mount::mnt_ns access] __do_sys_close fput_close_sync __fput dissolve_on_fput umount_tree class_namespace_excl_destructor namespace_unlock free_mnt_ns mnt_ns_tree_remove call_rcu(mnt_ns_release_rcu) mnt_ns_release_rcu mnt_ns_release kfree [mnt_namespace::user_ns access] **UAF** Fix it by taking rcu_read_lock() around the mount::mnt_ns access, like in __prepend_path(). Additionally, document the semantics of mount::mnt_ns, and use WRITE_ONCE() for writers that can race with lockless readers. This bug is unreachable unless one of the following is set: - CONFIG_PREEMPTION - CONFIG_RCU_STRICT_GRACE_PERIOD because it requires an RCU grace period to happen during a syscall without an explicit preemption. This doesn't seem to have interesting security impact; worst-case, it could leak the result of an integer comparison to userspace (from the level check in cap_capable()), cause an endless loop, or crash the kernel by dereferencing an invalid address.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Use After Free → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of serviceCWE-416
A

Official authority intelligence

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

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise das Auslösen eines Denial-of-Service-Zustands, die Umgehung von Sicherheitsmaßnahmen oder das Verursachen von Speicherbeschädigungen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260708Security Bulletin 8 July 2026 [PDF, 1MB]]

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 8 July 2026 [PDF, 1MB]], published on 8 July 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-53332 Référence CVE CVE-2026-53333 https://www.cve.org/CVERecord?id=CVE-2026-53333 Référence CVE CVE-2026-53334 https://www.cve.org/CVERecord?id=CVE-2026-53334 Référence CVE CVE-2026-53335 https://www.cve.org/CVERecord?id=CVE-2026-53335 Référence CVE CVE-2026-53336 https://www.cve.org/CVERecord?id=CVE-2026-53336 Référence CVE CVE-2026-53337 https://www.cve.org/CVERecord?id=CVE-2026-53337 Référence CVE CVE-2026-53338 https://www.cve.org/CVERecord?id=CVE-2026-53338 Référence CVE CVE-2026-53339 https://www.cve.org/CVERecord?id=CVE-2026-53339 Référence CVE CVE-2026-53340 https://www.cve.org/CVERecord?id=CVE-2026-53340 Référence CVE CVE-2026-53341 https://www.cve.org/CVERecord?id=CVE-2026-53341 Référence CVE CVE-2026-53342 https://www.cve.org/CVERecord?id=CVE-2026-53342 Référence CVE CVE-2026-53343 https://www.cve.org/CVERecord?id=CVE-2026-53343 Référence CVE CVE-2026-53344 https://www.cve.org/CVERecord?id=CVE-2026-53344 Référence CVE CVE-2026-53345 https://www.cve.org/CVERecord?id=CVE-2026-53345 Référence CVE CVE-2026-53346 https://www.cve.org/CVERecord?id=CVE-2026-53346 Référence CVE CVE-2026-53347 https://www.cve.org/CVERecord?id=CVE-2026-53347 Référence CVE CVE-2026-53348 https://www.cve.org/CVERecord?id=CVE-2026-53348 Référence CVE CVE-2026-53349 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52993 Référence CVE CVE-2026-53002 https://www.cve.org/CVERecord?id=CVE-2026-53002 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53166 https://www.cve.org/CVERecord?id=CVE-2026-53166 Référence CVE CVE-2026-53185 https://www.cve.org/CVERecord?id=CVE-2026-53185 Référence CVE CVE-2026-53239 https://www.cve.org/CVERecord?id=CVE-2026-53239 Référence CVE CVE-2026-53266 https://www.cve.org/CVERecord?id=CVE-2026-53266 Référence CVE CVE-2026-53341 https://www.cve.org/CVERecord?id=CVE-2026-53341 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=CVE-2026-63794 Référence CVE CVE-2026-63823 https://www.cve.org/CVERecord?id=CVE-2026-63823 Référence CVE CVE-2026-63875 https://www.cve.org/CVERecord?id=CVE-2026-63875 Référence CVE CVE-2026-63917 https://www.cve.org/CVERecord?id=CVE-2026-63917 Référence CVE CVE-2026-63919 https://www.cve.org/CVERecord?id=CVE-2026-63919 Référence CVE CVE-2026-63921 https://www.cve.org/CVERecord?id=CVE-2026-63921 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64102 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-53238 Référence CVE CVE-2026-53264 https://www.cve.org/CVERecord?id=CVE-2026-53264 Référence CVE CVE-2026-53269 https://www.cve.org/CVERecord?id=CVE-2026-53269 Référence CVE CVE-2026-53284 https://www.cve.org/CVERecord?id=CVE-2026-53284 Référence CVE CVE-2026-53291 https://www.cve.org/CVERecord?id=CVE-2026-53291 Référence CVE CVE-2026-53309 https://www.cve.org/CVERecord?id=CVE-2026-53309 Référence CVE CVE-2026-53330 https://www.cve.org/CVERecord?id=CVE-2026-53330 Référence CVE CVE-2026-53336 https://www.cve.org/CVERecord?id=CVE-2026-53336 Référence CVE CVE-2026-53337 https://www.cve.org/CVERecord?id=CVE-2026-53337 Référence CVE CVE-2026-53341 https://www.cve.org/CVERecord?id=CVE-2026-53341 Référence CVE CVE-2026-53353 https://www.cve.org/CVERecord?id=CVE-2026-53353 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=CVE-2026-53365 Référence CVE CVE-2026-53388 https://www.cve.org/CVERecord?id=CVE-2026-53388 Référence CVE CVE-2026-63801 https://www.cve.org/CVERecord?id=CVE-2026-63801 Référence CVE CVE-2026-63803 https://www.cve.org/CVERecord?id=CVE-2026-63803 Référence CVE CVE-2026-63804 https://www.cve.org/CVERecord?id=CVE-2026-63804 Référence CVE CVE-2026-63808 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-53332 Référence CVE CVE-2026-53333 https://www.cve.org/CVERecord?id=CVE-2026-53333 Référence CVE CVE-2026-53334 https://www.cve.org/CVERecord?id=CVE-2026-53334 Référence CVE CVE-2026-53335 https://www.cve.org/CVERecord?id=CVE-2026-53335 Référence CVE CVE-2026-53336 https://www.cve.org/CVERecord?id=CVE-2026-53336 Référence CVE CVE-2026-53337 https://www.cve.org/CVERecord?id=CVE-2026-53337 Référence CVE CVE-2026-53338 https://www.cve.org/CVERecord?id=CVE-2026-53338 Référence CVE CVE-2026-53339 https://www.cve.org/CVERecord?id=CVE-2026-53339 Référence CVE CVE-2026-53340 https://www.cve.org/CVERecord?id=CVE-2026-53340 Référence CVE CVE-2026-53341 https://www.cve.org/CVERecord?id=CVE-2026-53341 Référence CVE CVE-2026-53342 https://www.cve.org/CVERecord?id=CVE-2026-53342 Référence CVE CVE-2026-53343 https://www.cve.org/CVERecord?id=CVE-2026-53343 Référence CVE CVE-2026-53344 https://www.cve.org/CVERecord?id=CVE-2026-53344 Référence CVE CVE-2026-53345 https://www.cve.org/CVERecord?id=CVE-2026-53345 Référence CVE CVE-2026-53346 https://www.cve.org/CVERecord?id=CVE-2026-53346 Référence CVE CVE-2026-53347 https://www.cve.org/CVERecord?id=CVE-2026-53347 Référence CVE CVE-2026-53348 https://www.cve.org/CVERecord?id=CVE-2026-53348 Référence CVE CVE-2026-53349 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53332 Référence CVE CVE-2026-53333 https://www.cve.org/CVERecord?id=CVE-2026-53333 Référence CVE CVE-2026-53334 https://www.cve.org/CVERecord?id=CVE-2026-53334 Référence CVE CVE-2026-53335 https://www.cve.org/CVERecord?id=CVE-2026-53335 Référence CVE CVE-2026-53336 https://www.cve.org/CVERecord?id=CVE-2026-53336 Référence CVE CVE-2026-53337 https://www.cve.org/CVERecord?id=CVE-2026-53337 Référence CVE CVE-2026-53338 https://www.cve.org/CVERecord?id=CVE-2026-53338 Référence CVE CVE-2026-53339 https://www.cve.org/CVERecord?id=CVE-2026-53339 Référence CVE CVE-2026-53340 https://www.cve.org/CVERecord?id=CVE-2026-53340 Référence CVE CVE-2026-53341 https://www.cve.org/CVERecord?id=CVE-2026-53341 Référence CVE CVE-2026-53342 https://www.cve.org/CVERecord?id=CVE-2026-53342 Référence CVE CVE-2026-53343 https://www.cve.org/CVERecord?id=CVE-2026-53343 Référence CVE CVE-2026-53344 https://www.cve.org/CVERecord?id=CVE-2026-53344 Référence CVE CVE-2026-53345 https://www.cve.org/CVERecord?id=CVE-2026-53345 Référence CVE CVE-2026-53346 https://www.cve.org/CVERecord?id=CVE-2026-53346 Référence CVE CVE-2026-53347 https://www.cve.org/CVERecord?id=CVE-2026-53347 Référence CVE CVE-2026-53348 https://www.cve.org/CVERecord?id=CVE-2026-53348 Référence CVE CVE-2026-53349 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-53332 Référence CVE CVE-2026-53333 https://www.cve.org/CVERecord?id=CVE-2026-53333 Référence CVE CVE-2026-53334 https://www.cve.org/CVERecord?id=CVE-2026-53334 Référence CVE CVE-2026-53335 https://www.cve.org/CVERecord?id=CVE-2026-53335 Référence CVE CVE-2026-53336 https://www.cve.org/CVERecord?id=CVE-2026-53336 Référence CVE CVE-2026-53337 https://www.cve.org/CVERecord?id=CVE-2026-53337 Référence CVE CVE-2026-53338 https://www.cve.org/CVERecord?id=CVE-2026-53338 Référence CVE CVE-2026-53339 https://www.cve.org/CVERecord?id=CVE-2026-53339 Référence CVE CVE-2026-53340 https://www.cve.org/CVERecord?id=CVE-2026-53340 Référence CVE CVE-2026-53341 https://www.cve.org/CVERecord?id=CVE-2026-53341 Référence CVE CVE-2026-53342 https://www.cve.org/CVERecord?id=CVE-2026-53342 Référence CVE CVE-2026-53343 https://www.cve.org/CVERecord?id=CVE-2026-53343 Référence CVE CVE-2026-53344 https://www.cve.org/CVERecord?id=CVE-2026-53344 Référence CVE CVE-2026-53345 https://www.cve.org/CVERecord?id=CVE-2026-53345 Référence CVE CVE-2026-53346 https://www.cve.org/CVERecord?id=CVE-2026-53346 Référence CVE CVE-2026-53347 https://www.cve.org/CVERecord?id=CVE-2026-53347 Référence CVE CVE-2026-53348 https://www.cve.org/CVERecord?id=CVE-2026-53348 Référence CVE CVE-2026-53349 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-53309 Référence CVE CVE-2026-53314 https://www.cve.org/CVERecord?id=CVE-2026-53314 Référence CVE CVE-2026-53320 https://www.cve.org/CVERecord?id=CVE-2026-53320 Référence CVE CVE-2026-53325 https://www.cve.org/CVERecord?id=CVE-2026-53325 Référence CVE CVE-2026-53327 https://www.cve.org/CVERecord?id=CVE-2026-53327 Référence CVE CVE-2026-53329 https://www.cve.org/CVERecord?id=CVE-2026-53329 Référence CVE CVE-2026-53331 https://www.cve.org/CVERecord?id=CVE-2026-53331 Référence CVE CVE-2026-53337 https://www.cve.org/CVERecord?id=CVE-2026-53337 Référence CVE CVE-2026-53339 https://www.cve.org/CVERecord?id=CVE-2026-53339 Référence CVE CVE-2026-53341 https://www.cve.org/CVERecord?id=CVE-2026-53341 Référence CVE CVE-2026-53343 https://www.cve.org/CVERecord?id=CVE-2026-53343 Référence CVE CVE-2026-53349 https://www.cve.org/CVERecord?id=CVE-2026-53349 Référence CVE CVE-2026-53350 https://www.cve.org/CVERecord?id=CVE-2026-53350 Référence CVE CVE-2026-53352 https://www.cve.org/CVERecord?id=CVE-2026-53352 Référence CVE CVE-2026-53354 https://www.cve.org/CVERecord?id=CVE-2026-53354 Référence CVE CVE-2026-53355 https://www.cve.org/CVERecord?id=CVE-2026-53355 Référence CVE CVE-2026-53356 https://www.cve.org/CVERecord?id=CVE-2026-53356 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-024981LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、次の脆弱性が修正されました。fhandle: may_decode_fh()内でロックされていない-＞mnt_nsの読み取りによるUse-After-Free（UAF）を修正しました。may_decode_fh()はロックを保持せずにmount::mnt_nsにアクセスしていました。これは、マウントが同時にアンマウントされる可能性があり、mnt_namespaceがRCUの猶予期間後に同時に解放される可能性があることを意味します。この競合状態は、マウントポイントがopen_tree(..., OPEN_TREE_CLONE)によって作成されたと仮定すると、以下のように発生します。スレッド1　　　スレッド2　　　RCU　　　__do_sys_open_by_handle_at　　　do_handle_open　　　handle_to_path　　　may_decode_fh　　　is_mounted　　　[mount::mnt_nsアクセス]　　　[mount::mnt_nsアクセス]　　　__do_sys_close　fput_close_sync　__fput　dissolve_on_fput　umount_tree　class_namespace_excl_destructor　namespace_unlock　free_mnt_ns　mnt_ns_tree_remove　call_rcu(mnt_ns_release_rcu)　　　mnt_ns_release_rcu　　　mnt_ns_release　　　kfree　　　[mnt_namespace::user_nsアクセス]　　　**UAF**。この問題を修正するために、__prepend_path()のようにmount::mnt_nsアクセスの周囲でrcu_read_lock()を取得しています。さらに、mount::mnt_nsのセマンティクスを文書化し、ロックなしの読み取りと競合する可能性のある書き込みにはWRITE_ONCE()を使用しています。このバグは、以下のいずれかの設定が有効でなければ到達不可能です。- CONFIG_PREEMPTION - CONFIG_RCU_STRICT_GRACE_PERIOD。この設定は、システムコール中に明示的なプリエンプションなしでRCUの猶予期間が発生することを必要とします。この問題は、興味深いセキュリティ影響を及ぼさない可能性が高いです。最悪の場合、整数比較結果をユーザースペースに漏らす（cap_capable()のレベルチェックから）、無限ループを引き起こす、または無効なアドレスを参照してカーネルクラッシュを引き起こす可能性があります。

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: < 6.11, 6.12.95 ≤ 6.12.*, 6.18.36 ≤ 6.18.*, 7.0.13 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 1 Jul 2026 · Last source change 5 Aug 2026, 12:35 UTC · CWE-416 · Use After Free

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-40975
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

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