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

fsnotify: do not generate ACCESS/MODIFY events on child for special files

Linux · Linux

…UnscoredAssess manually
Recommended action
Patch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 25 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 severityUnscoredOperational priority:Needs assessment, manual assessment needed.unscored

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.21% 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: Manual assessmentRemediation target: Manual assessment

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 25 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.69-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.162-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.3-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.3-1Debian Security Tracker ↗Source updated 7 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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-2025-68788 · CSAF 2.0 · revision 36 · interimSUSE Product Security TeamCVE-2025-68788
331 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: fsnotify: do not generate ACCESS/MODIFY events on child for special files inotify/fanotify do not allow users with no read access to a file to subscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the same user to subscribe for watching events on children when the user has access to the parent directory (e.g. /dev). Users with no read access to a file but with read access to its parent directory can still stat the file and see if it was accessed/modified via atime/mtime change. The same is not true for special files (e.g. /dev/null). Users will not generally observe atime/mtime changes when other users read/write to special files, only when someone sets atime/mtime via utimensat(). Align fsnotify events with this stat behavior and do not generate ACCESS/MODIFY events to parent watchers on read/write of special files. The events are still generated to parent watchers on utimensat(). This closes some side-channels that could be possibly used for information exfiltration [1]. [1] https://snee.la/pdf/pubs/file-notification-attacks.pdf
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: fsnotify: do not generate ACCESS/MODIFY events on child for special files inotify/fanotify do not allow users with no read access to a file to subscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the same user to subscribe for watching events on children when the user has access to the parent directory (e.g. /dev). Users with no read access to a file but with read access to its parent directory can still stat the file and see if it was accessed/modified via atime/mtime change. The same is not true for special files (e.g. /dev/null). Users will not generally observe atime/mtime changes when other users read/write to special files, only when someone sets atime/mtime via utimensat(). Align fsnotify events with this stat behavior and do not generate ACCESS/MODIFY events to parent watchers on read/write of special files. The events are still generated to parent watchers on utimensat(). This closes some side-channels that could be possibly used for information exfiltration [1]. [1] https://snee.la/pdf/pubs/file-notification-attacks.pdf
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-2320

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: fsnotify: do not generate ACCESS/MODIFY events on child for special files inotify/fanotify do not allow users with no read access to a file to subscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the same user to subscribe for watching events on children when the user has access to the parent directory (e.g. /dev). Users with no read access to a file but with read access to its parent directory can still stat the file and see if it was accessed/modified via atime/mtime change. The same is not true for special files (e.g. /dev/null). Users will not generally observe atime/mtime changes when other users read/write to special files, only when someone sets atime/mtime via utimensat(). Align fsnotify events with this stat behavior and do not generate ACCESS/MODIFY events to parent watchers on read/write of special files. The events are still generated to parent watchers on utimensat(). This closes some side-channels that could be possibly used for information exfiltration [1]. [1] https://snee.la/pdf/pubs/file-notification-attacks.pdf

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
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 25 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: do not generate ACCESS/MODIFY events on child for special files inotify/fanotify do not allow users with no read access to a file to subscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the same user to subscribe for watching events on children when the user has access to the parent directory (e.g. /dev). Users with no read access to a file but with read access to its parent directory can still stat the file and see if it was accessed/modified via atime/mtime change. The same is not true for special files (e.g. /dev/null). Users will not generally observe atime/mtime changes when other users read/write to special files, only when someone sets atime/mtime via utimensat(). Align fsnotify events with this stat behavior and do not generate ACCESS/MODIFY events to parent watchers on read/write of special files. The events are still generated to parent watchers on utimensat(). This closes some side-channels that could be possibly used for information exfiltration [1]. [1] https://snee.la/pdf/pubs/file-notification-attacks.pdf

What

In the Linux kernel, the following vulnerability has been resolved: fsnotify: do not generate ACCESS/MODIFY events on child for special files inotify/fanotify do not allow users with no read access to a file to subscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the same user to subscribe for watching events on children when the user has access to the parent directory (e.g. /dev). Users with no read access to a file but with read access to its parent directory can still stat the file and see if it was accessed/modified via atime/mtime change. The same is not true for special files (e.g. /dev/null). Users will not generally observe atime/mtime changes when other users read/write to special files, only when someone sets atime/mtime via utimensat(). Align fsnotify events with this stat behavior and do not generate ACCESS/MODIFY events to parent watchers on read/write of special files. The events are still generated to parent watchers on utimensat(). This closes some side-channels that could be possibly used for information exfiltration [1]. [1] https://snee.la/pdf/pubs/file-notification-attacks.pdf

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 the affected interface may attempt exploitation when the stated preconditions are met. 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: do not generate ACCESS/MODIFY events on child for special files inotify/fanotify do not allow users with no read access to a file to subscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the same user to subscribe for watching events on children when the user has access to the parent directory (e.g. /dev). Users with no read access to a file but with read access to its parent directory can still stat the file and see if it was accessed/modified via atime/mtime change. The same is not true for special files (e.g. /dev/null). Users will not generally observe atime/mtime changes when other users read/write to special files, only when someone sets atime/mtime via utimensat(). Align fsnotify events with this stat behavior and do not generate ACCESS/MODIFY events to parent watchers on read/write of special files. The events are still generated to parent watchers on utimensat(). This closes some side-channels that could be possibly used for information exfiltration [1]. [1] https://snee.la/pdf/pubs/file-notification-attacks.pdf

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 the affected interface may attempt exploitation when the stated preconditions are met. 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
the affected interface → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
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.
Not available from the selected scoring authority.
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.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-2320Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: fsnotify: do not generate ACCESS/MODIFY events on child for special files inotify/fanotify do not allow users with no read access to a file to subscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the same user to subscribe for watching events on children when the user has access to the parent directory (e.g. /dev). Users with no read access to a file but with read access to its parent directory can still stat the file and see if it was accessed/modified via atime/mtime change. The same is not true for special files (e.g. /dev/null). Users will not generally observe atime/mtime changes when other users read/write to special files, only when someone sets atime/mtime via utimensat(). Align fsnotify events with this stat behavior and do not generate ACCESS/MODIFY events to parent watchers on read/write of special files. The events are still generated to parent watchers on utimensat(). This closes some side-channels that could be possibly used for information exfiltration [1]. [1] https://snee.la/pdf/pubs/file-notification-attacks.pdf

Official EUVD record ↗
BSI · German · WID-SEC-2026-0086Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260114Security Bulletin 14 Jan 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 14 Jan 2026, published on 14 January 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0880Multiples vulnérabilités dans les produits Siemens

25-39827, CVE-2025-39845, CVE-2025-39866, CVE-2025-39871, CVE-2025-39931, CVE-2025-39953, CVE-2025-39955, CVE-2025-39964, CVE-2025-39977, CVE-2025-39978, CVE-2025-39980, CVE-2025-40022, CVE-2025-40070, CVE-2025-40078, CVE-2025-40080, CVE-2025-40105, CVE-2025-40135, CVE-2025-40149, CVE-2025-40219, CVE-2025-40261, CVE-2025-40300, CVE-2025-61984, CVE-2025-61985, CVE-2025-68206, CVE-2025-68261, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291, CVE-2025-68337, CVE-2025-68349, CVE-2025-68363, CVE-2025-68371, CVE-2025-68724, CVE-2025-68725, CVE-2025-68742, CVE-2025-68764, CVE-2025-68773, CVE-2025-68776, CVE-2025-68782, CVE-2025-68787, CVE-2025-68788, CVE-2025-68798, CVE-2025-68803, CVE-2025-68814, CVE-2025-68816, CVE-2025-68818, CVE-2025-68820, CVE-2025-71064, CVE-2025-71075, CVE-2025-71079, CVE-2025-71085, CVE-2025-71086, CVE-2025-71088, CVE-2025-71095, CVE-2025-71097, CVE-2025-71098, CVE-2025-71104, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71120, CVE-2025-71123, CVE-2025-71131, CVE-2025-71161, CVE-2025-71162, CVE-2025-71163, CVE-2025-71185, CVE-2025-71186, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191, CVE-2025-71197, CVE-2025-71221, CVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2026-3497, CVE-2026-22977, CVE-2026-22979, CVE-2026-22980, CVE-2026-22982, CVE-2026-

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

d?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68778 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68781 https://www.cve.org/CVERecord?id=CVE-2025-68781 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68784 https://www.cve.org/CVERecord?id=CVE-2025-68784 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68791 https://www.cve.org/CVERecord?id=CVE-2025-68791 Référence CVE CVE-2025-68792 https://www.cve.org/CVERecord?id=CVE-2025-68792 Référence CVE CVE-2025-68793 https://www.cve.org/CVERecord?id=CVE-2025-68793 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68778 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68781 https://www.cve.org/CVERecord?id=CVE-2025-68781 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68784 https://www.cve.org/CVERecord?id=CVE-2025-68784 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68791 https://www.cve.org/CVERecord?id=CVE-2025-68791 Référence CVE CVE-2025-68792 https://www.cve.org/CVERecord?id=CVE-2025-68792 Référence CVE CVE-2025-68793 https://www.cve.org/CVERecord?id=CVE-2025-68793 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68771 Référence CVE CVE-2025-68774 https://www.cve.org/CVERecord?id=CVE-2025-68774 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68771 Référence CVE CVE-2025-68774 https://www.cve.org/CVERecord?id=CVE-2025-68774 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68771 Référence CVE CVE-2025-68774 https://www.cve.org/CVERecord?id=CVE-2025-68774 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68770 Référence CVE CVE-2025-68771 https://www.cve.org/CVERecord?id=CVE-2025-68771 Référence CVE CVE-2025-68773 https://www.cve.org/CVERecord?id=CVE-2025-68773 Référence CVE CVE-2025-68775 https://www.cve.org/CVERecord?id=CVE-2025-68775 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68789 https://www.cve.org/CVERecord?id=CVE-2025-68789 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68771 Référence CVE CVE-2025-68774 https://www.cve.org/CVERecord?id=CVE-2025-68774 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-68778 Référence CVE CVE-2025-68779 https://www.cve.org/CVERecord?id=CVE-2025-68779 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68781 https://www.cve.org/CVERecord?id=CVE-2025-68781 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-68778 Référence CVE CVE-2025-68779 https://www.cve.org/CVERecord?id=CVE-2025-68779 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68781 https://www.cve.org/CVERecord?id=CVE-2025-68781 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68770 Référence CVE CVE-2025-68771 https://www.cve.org/CVERecord?id=CVE-2025-68771 Référence CVE CVE-2025-68773 https://www.cve.org/CVERecord?id=CVE-2025-68773 Référence CVE CVE-2025-68775 https://www.cve.org/CVERecord?id=CVE-2025-68775 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68784 https://www.cve.org/CVERecord?id=CVE-2025-68784 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68789 https://www.cve.org/CVERecord?id=CVE-2025-68789 Référence CVE CVE-2025-68792 https://www.cve.org/CVERecord?id=CVE-2025-68792 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68766 Référence CVE CVE-2025-68768 https://www.cve.org/CVERecord?id=CVE-2025-68768 Référence CVE CVE-2025-68770 https://www.cve.org/CVERecord?id=CVE-2025-68770 Référence CVE CVE-2025-68771 https://www.cve.org/CVERecord?id=CVE-2025-68771 Référence CVE CVE-2025-68773 https://www.cve.org/CVERecord?id=CVE-2025-68773 Référence CVE CVE-2025-68775 https://www.cve.org/CVERecord?id=CVE-2025-68775 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68789 https://www.cve.org/CVERecord?id=CVE-2025-68789 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68802 https://www.cve.org/CVERecord?id=CVE-2025-68802 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68768 Référence CVE CVE-2025-68770 https://www.cve.org/CVERecord?id=CVE-2025-68770 Référence CVE CVE-2025-68771 https://www.cve.org/CVERecord?id=CVE-2025-68771 Référence CVE CVE-2025-68773 https://www.cve.org/CVERecord?id=CVE-2025-68773 Référence CVE CVE-2025-68774 https://www.cve.org/CVERecord?id=CVE-2025-68774 Référence CVE CVE-2025-68775 https://www.cve.org/CVERecord?id=CVE-2025-68775 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68789 https://www.cve.org/CVERecord?id=CVE-2025-68789 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68802 https://www.cve.org/CVERecord?id=CVE-2025-68802 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68781 https://www.cve.org/CVERecord?id=CVE-2025-68781 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68778 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68781 https://www.cve.org/CVERecord?id=CVE-2025-68781 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68784 https://www.cve.org/CVERecord?id=CVE-2025-68784 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68789 https://www.cve.org/CVERecord?id=CVE-2025-68789 Référence CVE CVE-2025-68792 https://www.cve.org/CVERecord?id=CVE-2025-68792 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 2.6.36, 5.10.248 ≤ 5.10.*, 5.15.198 ≤ 5.15.*, 6.1.160 ≤ 6.1.*, 6.6.120 ≤ 6.6.*, 6.12.64 ≤ 6.12.*, 6.18.3 ≤ 6.18.*, 6.19 ≤ *
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 13 Jan 2026 · Last source change 8 Sept 2026, 08:43 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceUnavailable
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-2320
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD not scheduled

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.
    Before
    no BlackTree article
    After
    1 BlackTree article
    BlackTree editorial ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    72acc854427948efed7a83da27f7dc3239ac9afc < df2711544b050aba703e6da418c53c7dc5d443ca; 72acc854427948efed7a83da27f7dc3239ac9afc < 859bdf438f01d9aa7f84b09c1202d548c7cad9e8; 72acc854427948efed7a83da27f7dc3239ac9afc < 6a7d7d96eeeab7af2bd01afbb3d9878a11a13d91; 72acc854427948efed7a83da27f7dc3239ac9afc < e0643d46759db8b84c0504a676043e5e341b6c81; 72acc854427948efed7a83da27f7dc3239ac9afc < 82f7416bcbd951549e758d15fc1a96a5afc2e900; 72acc854427948efed7a83da27f7dc3239ac9afc < 7a93edb23bcf07a3aaf8b598edfc2faa8fbcc0b6; 72acc854427948efed7a83da27f7dc3239ac9afc < 635bc4def026a24e071436f4f356ea08c0eed6ff; 2.6.36 · Fixed: < 2.6.36; 5.10.248 ≤ 5.10.*; 5.15.198 ≤ 5.15.*; 6.1.160 ≤ 6.1.*; 6.6.120 ≤ 6.6.*; 6.12.64 ≤ 6.12.*; 6.18.3 ≤ 6.18.*; 6.19 ≤ *
    After
    Linux: 72acc854427948efed7a83da27f7dc3239ac9afc < df2711544b050aba703e6da418c53c7dc5d443ca, 72acc854427948efed7a83da27f7dc3239ac9afc < 859bdf438f01d9aa7f84b09c1202d548c7cad9e8, 72acc854427948efed7a83da27f7dc3239ac9afc < 6a7d7d96eeeab7af2bd01afbb3d9878a11a13d91, 72acc854427948efed7a83da27f7dc3239ac9afc < e0643d46759db8b84c0504a676043e5e341b6c81, 72acc854427948efed7a83da27f7dc3239ac9afc < 82f7416bcbd951549e758d15fc1a96a5afc2e900, 72acc854427948efed7a83da27f7dc3239ac9afc < 7a93edb23bcf07a3aaf8b598edfc2faa8fbcc0b6, 72acc854427948efed7a83da27f7dc3239ac9afc < 635bc4def026a24e071436f4f356ea08c0eed6ff, 2.6.36 · Fixed: Linux: < 2.6.36, 5.10.248 ≤ 5.10.*, 5.15.198 ≤ 5.15.*, 6.1.160 ≤ 6.1.*, 6.6.120 ≤ 6.6.*, 6.12.64 ≤ 6.12.*, 6.18.3 ≤ 6.18.*, 6.19 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-2320↗Vendor CSAF · SUSE Product Security Team↗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-2025-68788 · cve.blacktree.nl