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

fsnotify: fix inode reference leak in fsnotify_recalc_mask()

Linux · Linux

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 24 Jun 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: No default targetRemediation target: Normal maintenance

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 21 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 21 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.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.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.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-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-52990 · CSAF 2.0 · revision 9 · interimSUSE Product Security TeamCVE-2026-52990
93 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
  • kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: fsnotify: fix inode reference leak in fsnotify_recalc_mask() fsnotify_recalc_mask() fails to handle the return value of __fsnotify_recalc_mask(), which may return an inode pointer that needs to be released via fsnotify_drop_object() when the connector's HAS_IREF flag transitions from set to cleared. This manifests as a hung task with the following call trace: INFO: task umount:1234 blocked for more than 120 seconds. Call Trace: __schedule schedule fsnotify_sb_delete generic_shutdown_super kill_anon_super cleanup_mnt task_work_run do_exit do_group_exit The race window that triggers the iref leak: Thread A (adding mark) Thread B (removing mark) ────────────────────── ──────────────────────── fsnotify_add_mark_locked(): fsnotify_add_mark_list(): spin_lock(conn->lock) add mark_B(evictable) to list spin_unlock(conn->lock) return /* ---- gap: no lock held ---- */ fsnotify_detach_mark(mark_A): spin_lock(mark_A->lock) clear ATTACHED flag on mark_A spin_unlock(mark_A->lock) fsnotify_put_mark(mark_A) fsnotify_recalc_mask(): spin_lock(conn->lock) __fsnotify_recalc_mask(): /* mark_A skipped: ATTACHED cleared */ /* only mark_B(evictable) remains */ want_iref = false has_iref = true /* not yet cleared */ -> HAS_IREF transitions true -> false -> returns inode pointer spin_unlock(conn->lock) /* BUG: return value discarded! * iput() and fsnotify_put_sb_watched_objects() * are never called */ Fix this by deferring the transition true -> false of HAS_IREF flag from fsnotify_recalc_mask() (Thread A) to fsnotify_put_mark() (thread B).
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-38858

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 21 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: fsnotify: fix inode reference leak in fsnotify_recalc_mask() fsnotify_recalc_mask() fails to handle the return value of __fsnotify_recalc_mask(), which may return an inode pointer that needs to be released via fsnotify_drop_object() when the connector's HAS_IREF flag transitions from set to cleared. This manifests as a hung task with the following call trace: INFO: task umount:1234 blocked for more than 120 seconds. Call Trace: __schedule schedule fsnotify_sb_delete generic_shutdown_super kill_anon_super cleanup_mnt task_work_run do_exit do_group_exit The race window that triggers the iref leak: Thread A (adding mark) Thread B (removing mark) ────────────────────── ──────────────────────── fsnotify_add_mark_locked(): fsnotify_add_mark_list(): spin_lock(conn->lock) add mark_B(evictable) to list spin_unlock(conn->lock) return /* ---- gap: no lock held ---- */ fsnotify_detach_mark(mark_A): spin_lock(mark_A->lock) clear ATTACHED flag on mark_A spin_unlock(mark_A->lock) fsnotify_put_mark(mark_A) fsnotify_recalc_mask(): spin_lock(conn->lock) __fsnotify_recalc_mask(): /* mark_A skipped: ATTACHED cleared */ /* only mark_B(evictable) remains */ want_iref = false has_iref = true /* not yet cleared */ -> HAS_IREF transitions true -> false -> returns inode pointer spin_unlock(conn->lock) /* BUG: return value discarded! * iput() and fsnotify_put_sb_watched_objects() * are never called */ Fix this by deferring the transition true -> false of HAS_IREF flag from fsnotify_recalc_mask() (Thread A) to fsnotify_put_mark() (thread B).

What

In the Linux kernel, the following vulnerability has been resolved: fsnotify: fix inode reference leak in fsnotify_recalc_mask() fsnotify_recalc_mask() fails to handle the return value of __fsnotify_recalc_mask(), which may return an inode pointer that needs to be released via fsnotify_drop_object() when the connector's HAS_IREF flag transitions from set to cleared. This manifests as a hung task with the following call trace: INFO: task umount:1234 blocked for more than 120 seconds. Call Trace: __schedule schedule fsnotify_sb_delete generic_shutdown_super kill_anon_super cleanup_mnt task_work_run do_exit do_group_exit The race window that triggers the iref leak: Thread A (adding mark) Thread B (removing mark) ────────────────────── ──────────────────────── fsnotify_add_mark_locked(): fsnotify_add_mark_list(): spin_lock(conn->lock) add mark_B(evictable) to list spin_unlock(conn->lock) return /* ---- gap: no lock held ---- */ fsnotify_detach_mark(mark_A): spin_lock(mark_A->lock) clear ATTACHED flag on mark_A spin_unlock(mark_A->lock) fsnotify_put_mark(mark_A) fsnotify_recalc_mask(): spin_lock(conn->lock) __fsnotify_recalc_mask(): /* mark_A skipped: ATTACHED cleared */ /* only mark_B(evictable) remains */ want_iref = false has_iref = true /* not yet cleared */ -> HAS_IREF transitions true -> false -> returns inode pointer spin_unlock(conn->lock) /* BUG: return value discarded! * iput() and fsnotify_put_sb_watched_objects() * are never called */ Fix this by deferring the transition true -> false of HAS_IREF flag from fsnotify_recalc_mask() (Thread A) to fsnotify_put_mark() (thread B).

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 local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: fsnotify: fix inode reference leak in fsnotify_recalc_mask() fsnotify_recalc_mask() fails to handle the return value of __fsnotify_recalc_mask(), which may return an inode pointer that needs to be released via fsnotify_drop_object() when the connector's HAS_IREF flag transitions from set to cleared. This manifests as a hung task with the following call trace: INFO: task umount:1234 blocked for more than 120 seconds. Call Trace: __schedule schedule fsnotify_sb_delete generic_shutdown_super kill_anon_super cleanup_mnt task_work_run do_exit do_group_exit The race window that triggers the iref leak: Thread A (adding mark) Thread B (removing mark) ────────────────────── ──────────────────────── fsnotify_add_mark_locked(): fsnotify_add_mark_list(): spin_lock(conn->lock) add mark_B(evictable) to list spin_unlock(conn->lock) return /* ---- gap: no lock held ---- */ fsnotify_detach_mark(mark_A): spin_lock(mark_A->lock) clear ATTACHED flag on mark_A spin_unlock(mark_A->lock) fsnotify_put_mark(mark_A) fsnotify_recalc_mask(): spin_lock(conn->lock) __fsnotify_recalc_mask(): /* mark_A skipped: ATTACHED cleared */ /* only mark_B(evictable) remains */ want_iref = false has_iref = true /* not yet cleared */ -> HAS_IREF transitions true -> false -> returns inode pointer spin_unlock(conn->lock) /* BUG: return value discarded! * iput() and fsnotify_put_sb_watched_objects() * are never called */ Fix this by deferring the transition true -> false of HAS_IREF flag from fsnotify_recalc_mask() (Thread A) to fsnotify_put_mark() (thread B).

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 local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
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:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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

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

Official authority intelligence

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

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

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 1 July 2026, published on 1 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-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52983 https://www.cve.org/CVERecord?id=CVE-2026-52983 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52987 https://www.cve.org/CVERecord?id=CVE-2026-52987 Référence CVE CVE-2026-52988 https://www.cve.org/CVERecord?id=CVE-2026-52988 Référence CVE CVE-2026-52989 https://www.cve.org/CVERecord?id=CVE-2026-52989 Référence CVE CVE-2026-52990 https://www.cve.org/CVERecord?id=CVE-2026-52990 Référence CVE CVE-2026-52991 https://www.cve.org/CVERecord?id=CVE-2026-52991 Référence CVE CVE-2026-52992 https://www.cve.org/CVERecord?id=CVE-2026-52992 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-52994 https://www.cve.org/CVERecord?id=CVE-2026-52994 Référence CVE CVE-2026-52995 https://www.cve.org/CVERecord?id=CVE-2026-52995 Référence CVE CVE-2026-52996 https://www.cve.org/CVERecord?id=CVE-2026-52996 Référence CVE CVE-2026-52997 https://www.cve.org/CVERecord?id=CVE-2026-52997 Référence CVE CVE-2026-52998 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-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=CVE-2026-52946 Référence CVE CVE-2026-52977 https://www.cve.org/CVERecord?id=CVE-2026-52977 Référence CVE CVE-2026-52990 https://www.cve.org/CVERecord?id=CVE-2026-52990 Référence CVE CVE-2026-52991 https://www.cve.org/CVERecord?id=CVE-2026-52991 Référence CVE CVE-2026-52994 https://www.cve.org/CVERecord?id=CVE-2026-52994 Référence CVE CVE-2026-53001 https://www.cve.org/CVERecord?id=CVE-2026-53001 Référence CVE CVE-2026-53031 https://www.cve.org/CVERecord?id=CVE-2026-53031 Référence CVE CVE-2026-53033 https://www.cve.org/CVERecord?id=CVE-2026-53033 Référence CVE CVE-2026-53034 https://www.cve.org/CVERecord?id=CVE-2026-53034 Référence CVE CVE-2026-53048 https://www.cve.org/CVERecord?id=CVE-2026-53048 Référence CVE CVE-2026-53059 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-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52983 https://www.cve.org/CVERecord?id=CVE-2026-52983 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52987 https://www.cve.org/CVERecord?id=CVE-2026-52987 Référence CVE CVE-2026-52988 https://www.cve.org/CVERecord?id=CVE-2026-52988 Référence CVE CVE-2026-52989 https://www.cve.org/CVERecord?id=CVE-2026-52989 Référence CVE CVE-2026-52990 https://www.cve.org/CVERecord?id=CVE-2026-52990 Référence CVE CVE-2026-52991 https://www.cve.org/CVERecord?id=CVE-2026-52991 Référence CVE CVE-2026-52992 https://www.cve.org/CVERecord?id=CVE-2026-52992 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-52994 https://www.cve.org/CVERecord?id=CVE-2026-52994 Référence CVE CVE-2026-52995 https://www.cve.org/CVERecord?id=CVE-2026-52995 Référence CVE CVE-2026-52996 https://www.cve.org/CVERecord?id=CVE-2026-52996 Référence CVE CVE-2026-52997 https://www.cve.org/CVERecord?id=CVE-2026-52997 Référence CVE CVE-2026-52998 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-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=CVE-2026-52946 Référence CVE CVE-2026-52955 https://www.cve.org/CVERecord?id=CVE-2026-52955 Référence CVE CVE-2026-52956 https://www.cve.org/CVERecord?id=CVE-2026-52956 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=CVE-2026-52975 Référence CVE CVE-2026-52977 https://www.cve.org/CVERecord?id=CVE-2026-52977 Référence CVE CVE-2026-52990 https://www.cve.org/CVERecord?id=CVE-2026-52990 Référence CVE CVE-2026-52994 https://www.cve.org/CVERecord?id=CVE-2026-52994 Référence CVE CVE-2026-53001 https://www.cve.org/CVERecord?id=CVE-2026-53001 Référence CVE CVE-2026-53033 https://www.cve.org/CVERecord?id=CVE-2026-53033 Référence CVE CVE-2026-53034 https://www.cve.org/CVERecord?id=CVE-2026-53034 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53076 https://www.cve.org/CVERecord?id=CVE-2026-53076 Référence CVE CVE-2026-53077 https://www.cve.org/CVERecord?id=CVE-2026-53077 Référence CVE CVE-2026-53089 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-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52983 https://www.cve.org/CVERecord?id=CVE-2026-52983 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52987 https://www.cve.org/CVERecord?id=CVE-2026-52987 Référence CVE CVE-2026-52988 https://www.cve.org/CVERecord?id=CVE-2026-52988 Référence CVE CVE-2026-52989 https://www.cve.org/CVERecord?id=CVE-2026-52989 Référence CVE CVE-2026-52990 https://www.cve.org/CVERecord?id=CVE-2026-52990 Référence CVE CVE-2026-52991 https://www.cve.org/CVERecord?id=CVE-2026-52991 Référence CVE CVE-2026-52992 https://www.cve.org/CVERecord?id=CVE-2026-52992 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-52994 https://www.cve.org/CVERecord?id=CVE-2026-52994 Référence CVE CVE-2026-52995 https://www.cve.org/CVERecord?id=CVE-2026-52995 Référence CVE CVE-2026-52996 https://www.cve.org/CVERecord?id=CVE-2026-52996 Référence CVE CVE-2026-52997 https://www.cve.org/CVERecord?id=CVE-2026-52997 Référence CVE CVE-2026-52998 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-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=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=CVE-2026-52946 Référence CVE CVE-2026-52956 https://www.cve.org/CVERecord?id=CVE-2026-52956 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=CVE-2026-52975 Référence CVE CVE-2026-52977 https://www.cve.org/CVERecord?id=CVE-2026-52977 Référence CVE CVE-2026-52990 https://www.cve.org/CVERecord?id=CVE-2026-52990 Référence CVE CVE-2026-52994 https://www.cve.org/CVERecord?id=CVE-2026-52994 Référence CVE CVE-2026-53001 https://www.cve.org/CVERecord?id=CVE-2026-53001 Référence CVE CVE-2026-53033 https://www.cve.org/CVERecord?id=CVE-2026-53033 Référence CVE CVE-2026-53034 https://www.cve.org/CVERecord?id=CVE-2026-53034 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53076 https://www.cve.org/CVERecord?id=CVE-2026-53076 Référence CVE CVE-2026-53077 https://www.cve.org/CVERecord?id=CVE-2026-53077 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52983 https://www.cve.org/CVERecord?id=CVE-2026-52983 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52987 https://www.cve.org/CVERecord?id=CVE-2026-52987 Référence CVE CVE-2026-52988 https://www.cve.org/CVERecord?id=CVE-2026-52988 Référence CVE CVE-2026-52989 https://www.cve.org/CVERecord?id=CVE-2026-52989 Référence CVE CVE-2026-52990 https://www.cve.org/CVERecord?id=CVE-2026-52990 Référence CVE CVE-2026-52991 https://www.cve.org/CVERecord?id=CVE-2026-52991 Référence CVE CVE-2026-52992 https://www.cve.org/CVERecord?id=CVE-2026-52992 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-52994 https://www.cve.org/CVERecord?id=CVE-2026-52994 Référence CVE CVE-2026-52995 https://www.cve.org/CVERecord?id=CVE-2026-52995 Référence CVE CVE-2026-52996 https://www.cve.org/CVERecord?id=CVE-2026-52996 Référence CVE CVE-2026-52997 https://www.cve.org/CVERecord?id=CVE-2026-52997 Référence CVE CVE-2026-52998 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-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52983 https://www.cve.org/CVERecord?id=CVE-2026-52983 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52987 https://www.cve.org/CVERecord?id=CVE-2026-52987 Référence CVE CVE-2026-52988 https://www.cve.org/CVERecord?id=CVE-2026-52988 Référence CVE CVE-2026-52989 https://www.cve.org/CVERecord?id=CVE-2026-52989 Référence CVE CVE-2026-52990 https://www.cve.org/CVERecord?id=CVE-2026-52990 Référence CVE CVE-2026-52991 https://www.cve.org/CVERecord?id=CVE-2026-52991 Référence CVE CVE-2026-52992 https://www.cve.org/CVERecord?id=CVE-2026-52992 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-52994 https://www.cve.org/CVERecord?id=CVE-2026-52994 Référence CVE CVE-2026-52995 https://www.cve.org/CVERecord?id=CVE-2026-52995 Référence CVE CVE-2026-52996 https://www.cve.org/CVERecord?id=CVE-2026-52996 Référence CVE CVE-2026-52997 https://www.cve.org/CVERecord?id=CVE-2026-52997 Référence CVE CVE-2026-52998 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-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52983 https://www.cve.org/CVERecord?id=CVE-2026-52983 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52987 https://www.cve.org/CVERecord?id=CVE-2026-52987 Référence CVE CVE-2026-52988 https://www.cve.org/CVERecord?id=CVE-2026-52988 Référence CVE CVE-2026-52989 https://www.cve.org/CVERecord?id=CVE-2026-52989 Référence CVE CVE-2026-52990 https://www.cve.org/CVERecord?id=CVE-2026-52990 Référence CVE CVE-2026-52991 https://www.cve.org/CVERecord?id=CVE-2026-52991 Référence CVE CVE-2026-52992 https://www.cve.org/CVERecord?id=CVE-2026-52992 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-52994 https://www.cve.org/CVERecord?id=CVE-2026-52994 Référence CVE CVE-2026-52995 https://www.cve.org/CVERecord?id=CVE-2026-52995 Référence CVE CVE-2026-52996 https://www.cve.org/CVERecord?id=CVE-2026-52996 Référence CVE CVE-2026-52997 https://www.cve.org/CVERecord?id=CVE-2026-52997 Référence CVE CVE-2026-52998 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。fsnotify: fsnotify_recalc_mask()におけるinode参照リークの修正です。fsnotify_recalc_mask()は__fsnotify_recalc_mask()の戻り値を適切に処理できておらず、connectorのHAS_IREFフラグがセットからクリアに遷移するときに、fsnotify_drop_object()で解放すべきinodeポインタを返す場合があります。この問題は、以下の呼び出しトレースを伴うタスクのハングとして現れます。 INFO: task umount:1234 が120秒以上ブロックされています。 Call Trace: __schedule schedule fsnotify_sb_delete generic_shutdown_super kill_anon_super cleanup_mnt task_work_run do_exit do_group_exit irefリークを引き起こすレースコンディションのタイミングは以下のとおりです。 スレッドA (マーク追加) スレッドB (マーク削除) ────────────────────── ──────────────────────── fsnotify_add_mark_locked(): fsnotify_add_mark_list(): spin_lock(conn-＞lock) listにevictableなmark_Bを追加 spin_unlock(conn-＞lock) return /* ---- ギャップ: ロックなし ---- */ fsnotify_detach_mark(mark_A): spin_lock(mark_A-＞lock) mark_AのATTACHEDフラグをクリア spin_unlock(mark_A-＞lock) fsnotify_put_mark(mark_A) fsnotify_recalc_mask(): spin_lock(conn-＞lock) __fsnotify_recalc_mask(): /* ATTACHEDがクリアされたためmark_Aはスキップされる */ /*mark_B(evictable)のみが残る*/ want_iref = false has_iref = true /* まだクリアされていない */ -＞ HAS_IREFがtrueからfalseへ遷移 -＞ inodeポインタを返す spin_unlock(conn-＞lock) /* バグ: 戻り値が破棄されている！ * iput()やfsnotify_put_sb_watched_objects()が呼ばれない */この問題は、fsnotify_recalc_mask()（スレッドA）におけるHAS_IREFフラグのtrueからfalseへの遷移を、fsnotify_put_mark()（スレッドB）によって遅延させることで修正されました。

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.19, 6.12.91 ≤ 6.12.*, 6.18.33 ≤ 6.18.*, 7.0.10 ≤ 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 24 Jun 2026 · Last source change 24 Jun 2026, 16:29 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-38858
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

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-38858↗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-52990 · cve.blacktree.nl