BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-23375High confidence

mm: thp: deny THP for files on anonymous inodes

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

20 package states
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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-23375 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: mm: thp: deny THP for files on anonymous inodes
616 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • kernel-64k-debug-debuginfo-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-debug-devel-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-debug-devel-matched-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-debuginfo-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-devel-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-devel-matched-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-debuginfo-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-debuginfo-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-debuginfo-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-debuginfo-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-devel-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-devel-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
Summary
A flaw was found in the Linux kernel's Transparent Huge Pages (THP) mechanism. This vulnerability occurs because the `file_thp_enabled()` function incorrectly allows THP for files on anonymous inodes, which are not designed for this feature. An attacker could potentially exploit this by manipulating specific memory operations, leading to a kernel crash when handling secret memory pages. Additionally, it can cause incorrect memory failure reports for guest memory files.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-15365

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: mm: thp: deny THP for files on anonymous inodes file_thp_enabled() incorrectly allows THP for files on anonymous inodes (e.g. guest_memfd and secretmem). These files are created via alloc_file_pseudo(), which does not call get_write_access() and leaves inode->i_writecount at 0. Combined with S_ISREG(inode->i_mode) being true, they appear as read-only regular files when CONFIG_READ_ONLY_THP_FOR_FS is enabled, making them eligible for THP collapse. Anonymous inodes can never pass the inode_is_open_for_write() check since their i_writecount is never incremented through the normal VFS open path. The right thing to do is to exclude them from THP eligibility altogether, since CONFIG_READ_ONLY_THP_FOR_FS was designed for real filesystem files (e.g. shared libraries), not for pseudo-filesystem inodes. For guest_memfd, this allows khugepaged and MADV_COLLAPSE to create large folios in the page cache via the collapse path, but the guest_memfd fault handler does not support large folios. This triggers WARN_ON_ONCE(folio_test_large(folio)) in kvm_gmem_fault_user_mapping(). For secretmem, collapse_file() tries to copy page contents through the direct map, but secretmem pages are removed from the direct map. This can result in a kernel crash: BUG: unable to handle page fault for address: ffff88810284d000 RIP: 0010:memcpy_orig+0x16/0x130 Call Trace: collapse_file hpage_collapse_scan_file madvise_collapse Secretmem is not affected by the crash on upstream as the memory failure recovery handles the failed copy gracefully, but it still triggers confusing false memory failure reports: Memory failure: 0x106d96f: recovery action for clean unevictable LRU page: Recovered Check IS_ANON_FILE(inode) in file_thp_enabled() to deny THP for all anonymous inode files.

What

In the Linux kernel, the following vulnerability has been resolved: mm: thp: deny THP for files on anonymous inodes file_thp_enabled() incorrectly allows THP for files on anonymous inodes (e.g. guest_memfd and secretmem). These files are created via alloc_file_pseudo(), which does not call get_write_access() and leaves inode->i_writecount at 0. Combined with S_ISREG(inode->i_mode) being true, they appear as read-only regular files when CONFIG_READ_ONLY_THP_FOR_FS is enabled, making them eligible for THP collapse. Anonymous inodes can never pass the inode_is_open_for_write() check since their i_writecount is never incremented through the normal VFS open path. The right thing to do is to exclude them from THP eligibility altogether, since CONFIG_READ_ONLY_THP_FOR_FS was designed for real filesystem files (e.g. shared libraries), not for pseudo-filesystem inodes. For guest_memfd, this allows khugepaged and MADV_COLLAPSE to create large folios in the page cache via the collapse path, but the guest_memfd fault handler does not support large folios. This triggers WARN_ON_ONCE(folio_test_large(folio)) in kvm_gmem_fault_user_mapping(). For secretmem, collapse_file() tries to copy page contents through the direct map, but secretmem pages are removed from the direct map. This can result in a kernel crash: BUG: unable to handle page fault for address: ffff88810284d000 RIP: 0010:memcpy_orig+0x16/0x130 Call Trace: collapse_file hpage_collapse_scan_file madvise_collapse Secretmem is not affected by the crash on upstream as the memory failure recovery handles the failed copy gracefully, but it still triggers confusing false memory failure reports: Memory failure: 0x106d96f: recovery action for clean unevictable LRU page: Recovered Check IS_ANON_FILE(inode) in file_thp_enabled() to deny THP for all anonymous inode files.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

How

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

What

In the Linux kernel, the following vulnerability has been resolved: mm: thp: deny THP for files on anonymous inodes file_thp_enabled() incorrectly allows THP for files on anonymous inodes (e.g. guest_memfd and secretmem). These files are created via alloc_file_pseudo(), which does not call get_write_access() and leaves inode->i_writecount at 0. Combined with S_ISREG(inode->i_mode) being true, they appear as read-only regular files when CONFIG_READ_ONLY_THP_FOR_FS is enabled, making them eligible for THP collapse. Anonymous inodes can never pass the inode_is_open_for_write() check since their i_writecount is never incremented through the normal VFS open path. The right thing to do is to exclude them from THP eligibility altogether, since CONFIG_READ_ONLY_THP_FOR_FS was designed for real filesystem files (e.g. shared libraries), not for pseudo-filesystem inodes. For guest_memfd, this allows khugepaged and MADV_COLLAPSE to create large folios in the page cache via the collapse path, but the guest_memfd fault handler does not support large folios. This triggers WARN_ON_ONCE(folio_test_large(folio)) in kvm_gmem_fault_user_mapping(). For secretmem, collapse_file() tries to copy page contents through the direct map, but secretmem pages are removed from the direct map. This can result in a kernel crash: BUG: unable to handle page fault for address: ffff88810284d000 RIP: 0010:memcpy_orig+0x16/0x130 Call Trace: collapse_file hpage_collapse_scan_file madvise_collapse Secretmem is not affected by the crash on upstream as the memory failure recovery handles the failed copy gracefully, but it still triggers confusing false memory failure reports: Memory failure: 0x106d96f: recovery action for clean unevictable LRU page: Recovered Check IS_ANON_FILE(inode) in file_thp_enabled() to deny THP for all anonymous inode files.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

How

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

02

Exploit reality and attack path

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

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

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

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

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

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

CWE-617: Reachable Assertion. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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.
Denial of serviceCWE-617
A

Official authority intelligence

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

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

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, weitere nicht spezifizierte Auswirkungen zu verursachen und potentiell Code auszuführen.

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

d?id=CVE-2026-23363 Référence CVE CVE-2026-23364 https://www.cve.org/CVERecord?id=CVE-2026-23364 Référence CVE CVE-2026-23365 https://www.cve.org/CVERecord?id=CVE-2026-23365 Référence CVE CVE-2026-23367 https://www.cve.org/CVERecord?id=CVE-2026-23367 Référence CVE CVE-2026-23368 https://www.cve.org/CVERecord?id=CVE-2026-23368 Référence CVE CVE-2026-23369 https://www.cve.org/CVERecord?id=CVE-2026-23369 Référence CVE CVE-2026-23370 https://www.cve.org/CVERecord?id=CVE-2026-23370 Référence CVE CVE-2026-23372 https://www.cve.org/CVERecord?id=CVE-2026-23372 Référence CVE CVE-2026-23374 https://www.cve.org/CVERecord?id=CVE-2026-23374 Référence CVE CVE-2026-23375 https://www.cve.org/CVERecord?id=CVE-2026-23375 Référence CVE CVE-2026-23378 https://www.cve.org/CVERecord?id=CVE-2026-23378 Référence CVE CVE-2026-23379 https://www.cve.org/CVERecord?id=CVE-2026-23379 Référence CVE CVE-2026-23381 https://www.cve.org/CVERecord?id=CVE-2026-23381 Référence CVE CVE-2026-23382 https://www.cve.org/CVERecord?id=CVE-2026-23382 Référence CVE CVE-2026-23383 https://www.cve.org/CVERecord?id=CVE-2026-23383 Référence CVE CVE-2026-23386 https://www.cve.org/CVERecord?id=CVE-2026-23386 Référence CVE CVE-2026-23387 https://www.cve.org/CVERecord?id=CVE-2026-23387 Référence CVE CVE-2026-23388 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-23363 Référence CVE CVE-2026-23364 https://www.cve.org/CVERecord?id=CVE-2026-23364 Référence CVE CVE-2026-23365 https://www.cve.org/CVERecord?id=CVE-2026-23365 Référence CVE CVE-2026-23367 https://www.cve.org/CVERecord?id=CVE-2026-23367 Référence CVE CVE-2026-23368 https://www.cve.org/CVERecord?id=CVE-2026-23368 Référence CVE CVE-2026-23369 https://www.cve.org/CVERecord?id=CVE-2026-23369 Référence CVE CVE-2026-23370 https://www.cve.org/CVERecord?id=CVE-2026-23370 Référence CVE CVE-2026-23372 https://www.cve.org/CVERecord?id=CVE-2026-23372 Référence CVE CVE-2026-23374 https://www.cve.org/CVERecord?id=CVE-2026-23374 Référence CVE CVE-2026-23375 https://www.cve.org/CVERecord?id=CVE-2026-23375 Référence CVE CVE-2026-23378 https://www.cve.org/CVERecord?id=CVE-2026-23378 Référence CVE CVE-2026-23379 https://www.cve.org/CVERecord?id=CVE-2026-23379 Référence CVE CVE-2026-23381 https://www.cve.org/CVERecord?id=CVE-2026-23381 Référence CVE CVE-2026-23382 https://www.cve.org/CVERecord?id=CVE-2026-23382 Référence CVE CVE-2026-23383 https://www.cve.org/CVERecord?id=CVE-2026-23383 Référence CVE CVE-2026-23386 https://www.cve.org/CVERecord?id=CVE-2026-23386 Référence CVE CVE-2026-23387 https://www.cve.org/CVERecord?id=CVE-2026-23387 Référence CVE CVE-2026-23388 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-23363 Référence CVE CVE-2026-23364 https://www.cve.org/CVERecord?id=CVE-2026-23364 Référence CVE CVE-2026-23365 https://www.cve.org/CVERecord?id=CVE-2026-23365 Référence CVE CVE-2026-23367 https://www.cve.org/CVERecord?id=CVE-2026-23367 Référence CVE CVE-2026-23368 https://www.cve.org/CVERecord?id=CVE-2026-23368 Référence CVE CVE-2026-23369 https://www.cve.org/CVERecord?id=CVE-2026-23369 Référence CVE CVE-2026-23370 https://www.cve.org/CVERecord?id=CVE-2026-23370 Référence CVE CVE-2026-23372 https://www.cve.org/CVERecord?id=CVE-2026-23372 Référence CVE CVE-2026-23374 https://www.cve.org/CVERecord?id=CVE-2026-23374 Référence CVE CVE-2026-23375 https://www.cve.org/CVERecord?id=CVE-2026-23375 Référence CVE CVE-2026-23378 https://www.cve.org/CVERecord?id=CVE-2026-23378 Référence CVE CVE-2026-23379 https://www.cve.org/CVERecord?id=CVE-2026-23379 Référence CVE CVE-2026-23381 https://www.cve.org/CVERecord?id=CVE-2026-23381 Référence CVE CVE-2026-23382 https://www.cve.org/CVERecord?id=CVE-2026-23382 Référence CVE CVE-2026-23383 https://www.cve.org/CVERecord?id=CVE-2026-23383 Référence CVE CVE-2026-23386 https://www.cve.org/CVERecord?id=CVE-2026-23386 Référence CVE CVE-2026-23387 https://www.cve.org/CVERecord?id=CVE-2026-23387 Référence CVE CVE-2026-23388 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23363 Référence CVE CVE-2026-23365 https://www.cve.org/CVERecord?id=CVE-2026-23365 Référence CVE CVE-2026-23367 https://www.cve.org/CVERecord?id=CVE-2026-23367 Référence CVE CVE-2026-23368 https://www.cve.org/CVERecord?id=CVE-2026-23368 Référence CVE CVE-2026-23369 https://www.cve.org/CVERecord?id=CVE-2026-23369 Référence CVE CVE-2026-23370 https://www.cve.org/CVERecord?id=CVE-2026-23370 Référence CVE CVE-2026-23372 https://www.cve.org/CVERecord?id=CVE-2026-23372 Référence CVE CVE-2026-23373 https://www.cve.org/CVERecord?id=CVE-2026-23373 Référence CVE CVE-2026-23374 https://www.cve.org/CVERecord?id=CVE-2026-23374 Référence CVE CVE-2026-23375 https://www.cve.org/CVERecord?id=CVE-2026-23375 Référence CVE CVE-2026-23378 https://www.cve.org/CVERecord?id=CVE-2026-23378 Référence CVE CVE-2026-23382 https://www.cve.org/CVERecord?id=CVE-2026-23382 Référence CVE CVE-2026-23383 https://www.cve.org/CVERecord?id=CVE-2026-23383 Référence CVE CVE-2026-23387 https://www.cve.org/CVERecord?id=CVE-2026-23387 Référence CVE CVE-2026-23391 https://www.cve.org/CVERecord?id=CVE-2026-23391 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23393 https://www.cve.org/CVERecord?id=CVE-2026-23393 Référence CVE CVE-2026-23395 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23364 Référence CVE CVE-2026-23365 https://www.cve.org/CVERecord?id=CVE-2026-23365 Référence CVE CVE-2026-23367 https://www.cve.org/CVERecord?id=CVE-2026-23367 Référence CVE CVE-2026-23368 https://www.cve.org/CVERecord?id=CVE-2026-23368 Référence CVE CVE-2026-23369 https://www.cve.org/CVERecord?id=CVE-2026-23369 Référence CVE CVE-2026-23370 https://www.cve.org/CVERecord?id=CVE-2026-23370 Référence CVE CVE-2026-23372 https://www.cve.org/CVERecord?id=CVE-2026-23372 Référence CVE CVE-2026-23373 https://www.cve.org/CVERecord?id=CVE-2026-23373 Référence CVE CVE-2026-23374 https://www.cve.org/CVERecord?id=CVE-2026-23374 Référence CVE CVE-2026-23375 https://www.cve.org/CVERecord?id=CVE-2026-23375 Référence CVE CVE-2026-23378 https://www.cve.org/CVERecord?id=CVE-2026-23378 Référence CVE CVE-2026-23379 https://www.cve.org/CVERecord?id=CVE-2026-23379 Référence CVE CVE-2026-23380 https://www.cve.org/CVERecord?id=CVE-2026-23380 Référence CVE CVE-2026-23381 https://www.cve.org/CVERecord?id=CVE-2026-23381 Référence CVE CVE-2026-23382 https://www.cve.org/CVERecord?id=CVE-2026-23382 Référence CVE CVE-2026-23383 https://www.cve.org/CVERecord?id=CVE-2026-23383 Référence CVE CVE-2026-23386 https://www.cve.org/CVERecord?id=CVE-2026-23386 Référence CVE CVE-2026-23387 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.
Patch available
Affected
7fbb5e188248c50f737720825da1864ce42536d1 < 08de46a75f91a6661bc1ce0a93614f4bc313c581; 7fbb5e188248c50f737720825da1864ce42536d1 < 0524ee56af2c9bfbad152a810f1ca95de8ca00d7; 7fbb5e188248c50f737720825da1864ce42536d1 < f6fa05f0dddd387417d0c28281ddb951582514d6; 7fbb5e188248c50f737720825da1864ce42536d1 < dd085fe9a8ebfc5d10314c60452db38d2b75e609; 6.8
Fixed
kernel-64k-debug-debuginfo-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-debug-devel-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-debug-devel-matched-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-debuginfo-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-devel-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-devel-matched-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-debuginfo-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-debuginfo-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-debuginfo-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-debuginfo-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-matched-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-matched-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-matched-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-matched-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-common-aarch64-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-common-ppc64le-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-common-s390x-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-common-x86_64-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); and 586 more
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 25 Mar 2026 · Last source change 11 May 2026, 22:05 UTC · CWE-617 · Reachable Assertion

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-15365
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-15365↗Vendor CSAF · Red Hat Product Security↗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-23375 · cve.blacktree.nl