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

isofs: bound Rock Ridge symlink components to the SL record

Linux · Linux

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 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 severityHighOperational priority:Medium, lowered one band.downgradedsince 8 Sep 2026

Evidence used

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

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

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

25 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.96-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.180-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.100-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 5 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.

2 current
CVE-2026-64317 · CSAF 2.0 · revision 15 · interimSUSE Product Security TeamCVE-2026-64317
302 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 High Availability Extension 16.1
Summary
In the Linux kernel, the following vulnerability has been resolved: isofs: bound Rock Ridge symlink components to the SL record get_symlink_chunk() and the SL handling in parse_rock_ridge_inode_internal() walk the variable-length components of a Rock Ridge "SL" (symbolic link) record. Each component is a two-byte header (flags, len) followed by len bytes of text, so it occupies slp->len + 2 bytes. Both loops read slp->len and advance to the next component, and get_symlink_chunk() additionally does memcpy(rpnt, slp->text, slp->len), but neither checks that the component lies within the SL record before dereferencing it. A crafted SL record whose component declares a len that runs past the record (rr->len) therefore triggers an out-of-bounds read of up to 255 bytes. When the record sits at the tail of its backing buffer - for example a small kmalloc()ed continuation block reached through a CE record - the read crosses the allocation; get_symlink_chunk() then copies the out-of-bounds bytes into the symlink body returned to user space by readlink(), disclosing adjacent kernel memory. ISO 9660 images are routinely mounted from untrusted removable media - desktop environments auto-mount them (e.g. via udisks2) without CAP_SYS_ADMIN - so the record contents are attacker-controlled. Reject any component that does not fit in the remaining record bytes before using it. In get_symlink_chunk() return NULL, like the existing output-buffer (plimit) checks, so a malformed record makes readlink() fail with -EIO rather than silently returning a truncated target; in parse_rock_ridge_inode_internal() stop the inode-size walk.
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: isofs: bound Rock Ridge symlink components to the SL record get_symlink_chunk() and the SL handling in parse_rock_ridge_inode_internal() walk the variable-length components of a Rock Ridge "SL" (symbolic link) record. Each component is a two-byte header (flags, len) followed by len bytes of text, so it occupies slp->len + 2 bytes. Both loops read slp->len and advance to the next component, and get_symlink_chunk() additionally does memcpy(rpnt, slp->text, slp->len), but neither checks that the component lies within the SL record before dereferencing it. A crafted SL record whose component declares a len that runs past the record (rr->len) therefore triggers an out-of-bounds read of up to 255 bytes. When the record sits at the tail of its backing buffer - for example a small kmalloc()ed continuation block reached through a CE record - the read crosses the allocation; get_symlink_chunk() then copies the out-of-bounds bytes into the symlink body returned to user space by readlink(), disclosing adjacent kernel memory. ISO 9660 images are routinely mounted from untrusted removable media - desktop environments auto-mount them (e.g. via udisks2) without CAP_SYS_ADMIN - so the record contents are attacker-controlled. Reject any component that does not fit in the remaining record bytes before using it. In get_symlink_chunk() return NULL, like the existing output-buffer (plimit) checks, so a malformed record makes readlink() fail with -EIO rather than silently returning a truncated target; in parse_rock_ridge_inode_internal() stop the inode-size walk.
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-49029

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: isofs: bound Rock Ridge symlink components to the SL record get_symlink_chunk() and the SL handling in parse_rock_ridge_inode_internal() walk the variable-length components of a Rock Ridge "SL" (symbolic link) record. Each component is a two-byte header (flags, len) followed by len bytes of text, so it occupies slp->len + 2 bytes. Both loops read slp->len and advance to the next component, and get_symlink_chunk() additionally does memcpy(rpnt, slp->text, slp->len), but neither checks that the component lies within the SL record before dereferencing it. A crafted SL record whose component declares a len that runs past the record (rr->len) therefore triggers an out-of-bounds read of up to 255 bytes. When the record sits at the tail of its backing buffer - for example a small kmalloc()ed continuation block reached through a CE record - the read crosses the allocation; get_symlink_chunk() then copies the out-of-bounds bytes into the symlink body returned to user space by readlink(), disclosing adjacent kernel memory. ISO 9660 images are routinely mounted from untrusted removable media - desktop environments auto-mount them (e.g. via udisks2) without CAP_SYS_ADMIN - so the record contents are attacker-controlled. Reject any component that does not fit in the remaining record bytes before using it. In get_symlink_chunk() return NULL, like the existing output-buffer (plimit) checks, so a malformed record makes readlink() fail with -EIO rather than silently returning a truncated target; in parse_rock_ridge_inode_internal() stop the inode-size walk.

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 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: isofs: bound Rock Ridge symlink components to the SL record get_symlink_chunk() and the SL handling in parse_rock_ridge_inode_internal() walk the variable-length components of a Rock Ridge "SL" (symbolic link) record. Each component is a two-byte header (flags, len) followed by len bytes of text, so it occupies slp->len + 2 bytes. Both loops read slp->len and advance to the next component, and get_symlink_chunk() additionally does memcpy(rpnt, slp->text, slp->len), but neither checks that the component lies within the SL record before dereferencing it. A crafted SL record whose component declares a len that runs past the record (rr->len) therefore triggers an out-of-bounds read of up to 255 bytes. When the record sits at the tail of its backing buffer - for example a small kmalloc()ed continuation block reached through a CE record - the read crosses the allocation; get_symlink_chunk() then copies the out-of-bounds bytes into the symlink body returned to user space by readlink(), disclosing adjacent kernel memory. ISO 9660 images are routinely mounted from untrusted removable media - desktop environments auto-mount them (e.g. via udisks2) without CAP_SYS_ADMIN - so the record contents are attacker-controlled. Reject any component that does not fit in the remaining record bytes before using it. In get_symlink_chunk() return NULL, like the existing output-buffer (plimit) checks, so a malformed record makes readlink() fail with -EIO rather than silently returning a truncated target; in parse_rock_ridge_inode_internal() stop the inode-size walk.

What

In the Linux kernel, the following vulnerability has been resolved: isofs: bound Rock Ridge symlink components to the SL record get_symlink_chunk() and the SL handling in parse_rock_ridge_inode_internal() walk the variable-length components of a Rock Ridge "SL" (symbolic link) record. Each component is a two-byte header (flags, len) followed by len bytes of text, so it occupies slp->len + 2 bytes. Both loops read slp->len and advance to the next component, and get_symlink_chunk() additionally does memcpy(rpnt, slp->text, slp->len), but neither checks that the component lies within the SL record before dereferencing it. A crafted SL record whose component declares a len that runs past the record (rr->len) therefore triggers an out-of-bounds read of up to 255 bytes. When the record sits at the tail of its backing buffer - for example a small kmalloc()ed continuation block reached through a CE record - the read crosses the allocation; get_symlink_chunk() then copies the out-of-bounds bytes into the symlink body returned to user space by readlink(), disclosing adjacent kernel memory. ISO 9660 images are routinely mounted from untrusted removable media - desktop environments auto-mount them (e.g. via udisks2) without CAP_SYS_ADMIN - so the record contents are attacker-controlled. Reject any component that does not fit in the remaining record bytes before using it. In get_symlink_chunk() return NULL, like the existing output-buffer (plimit) checks, so a malformed record makes readlink() fail with -EIO rather than silently returning a truncated target; in parse_rock_ridge_inode_internal() stop the inode-size walk.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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: isofs: bound Rock Ridge symlink components to the SL record get_symlink_chunk() and the SL handling in parse_rock_ridge_inode_internal() walk the variable-length components of a Rock Ridge "SL" (symbolic link) record. Each component is a two-byte header (flags, len) followed by len bytes of text, so it occupies slp->len + 2 bytes. Both loops read slp->len and advance to the next component, and get_symlink_chunk() additionally does memcpy(rpnt, slp->text, slp->len), but neither checks that the component lies within the SL record before dereferencing it. A crafted SL record whose component declares a len that runs past the record (rr->len) therefore triggers an out-of-bounds read of up to 255 bytes. When the record sits at the tail of its backing buffer - for example a small kmalloc()ed continuation block reached through a CE record - the read crosses the allocation; get_symlink_chunk() then copies the out-of-bounds bytes into the symlink body returned to user space by readlink(), disclosing adjacent kernel memory. ISO 9660 images are routinely mounted from untrusted removable media - desktop environments auto-mount them (e.g. via udisks2) without CAP_SYS_ADMIN - so the record contents are attacker-controlled. Reject any component that does not fit in the remaining record bytes before using it. In get_symlink_chunk() return NULL, like the existing output-buffer (plimit) checks, so a malformed record makes readlink() fail with -EIO rather than silently returning a truncated target; in parse_rock_ridge_inode_internal() stop the inode-size walk.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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 → Out-of-bounds Read → 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: a standard category for the underlying weakness.
CWE-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I: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.CHighConfidentiality impact: A successful attack can cause a major loss.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.
CWE-125
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-49029Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: isofs: bound Rock Ridge symlink components to the SL record get_symlink_chunk() and the SL handling in parse_rock_ridge_inode_internal() walk the variable-length components of a Rock Ridge "SL" (symbolic link) record. Each component is a two-byte header (flags, len) followed by len bytes of text, so it occupies slp->len + 2 bytes. Both loops read slp->len and advance to the next component, and get_symlink_chunk() additionally does memcpy(rpnt, slp->text, slp->len), but neither checks that the component lies within the SL record before dereferencing it. A crafted SL record whose component declares a len that runs past the record (rr->len) therefore triggers an out-of-bounds read of up to 255 bytes. When the record sits at the tail of its backing buffer - for example a small kmalloc()ed continuation block reached through a CE record - the read crosses the allocation; get_symlink_chunk() then copies the out-of-bounds bytes into the symlink body returned to user space by readlink(), disclosing adjacent kernel memory. ISO 9660 images are routinely mounted from untrusted removable media - desktop environments auto-mount them (e.g. via udisks2) without CAP_SYS_ADMIN - so the record contents are attacker-controlled. Reject any component that does not fit in the remaining record bytes before using it. In get_symlink_chunk() return NULL, like the existing output-buffer (plimit) checks, so a malformed record makes readlink() fail with -EIO rather than silently returning a truncated target; in parse_rock_ridge_inode_internal() stop the inode-size walk.

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260729Security Bulletin 29 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Jul 2026, published on 29 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-64307 Référence CVE CVE-2026-64308 https://www.cve.org/CVERecord?id=CVE-2026-64308 Référence CVE CVE-2026-64309 https://www.cve.org/CVERecord?id=CVE-2026-64309 Référence CVE CVE-2026-64310 https://www.cve.org/CVERecord?id=CVE-2026-64310 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=CVE-2026-64313 Référence CVE CVE-2026-64314 https://www.cve.org/CVERecord?id=CVE-2026-64314 Référence CVE CVE-2026-64315 https://www.cve.org/CVERecord?id=CVE-2026-64315 Référence CVE CVE-2026-64316 https://www.cve.org/CVERecord?id=CVE-2026-64316 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64318 https://www.cve.org/CVERecord?id=CVE-2026-64318 Référence CVE CVE-2026-64319 https://www.cve.org/CVERecord?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64325 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-64306 Référence CVE CVE-2026-64307 https://www.cve.org/CVERecord?id=CVE-2026-64307 Référence CVE CVE-2026-64308 https://www.cve.org/CVERecord?id=CVE-2026-64308 Référence CVE CVE-2026-64309 https://www.cve.org/CVERecord?id=CVE-2026-64309 Référence CVE CVE-2026-64310 https://www.cve.org/CVERecord?id=CVE-2026-64310 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=CVE-2026-64313 Référence CVE CVE-2026-64315 https://www.cve.org/CVERecord?id=CVE-2026-64315 Référence CVE CVE-2026-64316 https://www.cve.org/CVERecord?id=CVE-2026-64316 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64319 https://www.cve.org/CVERecord?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64326 https://www.cve.org/CVERecord?id=CVE-2026-64326 Référence CVE CVE-2026-64327 https://www.cve.org/CVERecord?id=CVE-2026-64327 Référence CVE CVE-2026-64328 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-64307 Référence CVE CVE-2026-64308 https://www.cve.org/CVERecord?id=CVE-2026-64308 Référence CVE CVE-2026-64309 https://www.cve.org/CVERecord?id=CVE-2026-64309 Référence CVE CVE-2026-64310 https://www.cve.org/CVERecord?id=CVE-2026-64310 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=CVE-2026-64313 Référence CVE CVE-2026-64314 https://www.cve.org/CVERecord?id=CVE-2026-64314 Référence CVE CVE-2026-64315 https://www.cve.org/CVERecord?id=CVE-2026-64315 Référence CVE CVE-2026-64316 https://www.cve.org/CVERecord?id=CVE-2026-64316 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64318 https://www.cve.org/CVERecord?id=CVE-2026-64318 Référence CVE CVE-2026-64319 https://www.cve.org/CVERecord?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64325 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64178 Référence CVE CVE-2026-64190 https://www.cve.org/CVERecord?id=CVE-2026-64190 Référence CVE CVE-2026-64266 https://www.cve.org/CVERecord?id=CVE-2026-64266 Référence CVE CVE-2026-64268 https://www.cve.org/CVERecord?id=CVE-2026-64268 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64306 https://www.cve.org/CVERecord?id=CVE-2026-64306 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=CVE-2026-64313 Référence CVE CVE-2026-64315 https://www.cve.org/CVERecord?id=CVE-2026-64315 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64340 https://www.cve.org/CVERecord?id=CVE-2026-64340 Référence CVE CVE-2026-64341 https://www.cve.org/CVERecord?id=CVE-2026-64341 Référence CVE CVE-2026-64343 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-64296 Référence CVE CVE-2026-64303 https://www.cve.org/CVERecord?id=CVE-2026-64303 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64305 https://www.cve.org/CVERecord?id=CVE-2026-64305 Référence CVE CVE-2026-64306 https://www.cve.org/CVERecord?id=CVE-2026-64306 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=CVE-2026-64313 Référence CVE CVE-2026-64315 https://www.cve.org/CVERecord?id=CVE-2026-64315 Référence CVE CVE-2026-64316 https://www.cve.org/CVERecord?id=CVE-2026-64316 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64307 Référence CVE CVE-2026-64308 https://www.cve.org/CVERecord?id=CVE-2026-64308 Référence CVE CVE-2026-64309 https://www.cve.org/CVERecord?id=CVE-2026-64309 Référence CVE CVE-2026-64310 https://www.cve.org/CVERecord?id=CVE-2026-64310 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=CVE-2026-64313 Référence CVE CVE-2026-64314 https://www.cve.org/CVERecord?id=CVE-2026-64314 Référence CVE CVE-2026-64315 https://www.cve.org/CVERecord?id=CVE-2026-64315 Référence CVE CVE-2026-64316 https://www.cve.org/CVERecord?id=CVE-2026-64316 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64318 https://www.cve.org/CVERecord?id=CVE-2026-64318 Référence CVE CVE-2026-64319 https://www.cve.org/CVERecord?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64325 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-64307 Référence CVE CVE-2026-64308 https://www.cve.org/CVERecord?id=CVE-2026-64308 Référence CVE CVE-2026-64309 https://www.cve.org/CVERecord?id=CVE-2026-64309 Référence CVE CVE-2026-64310 https://www.cve.org/CVERecord?id=CVE-2026-64310 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=CVE-2026-64313 Référence CVE CVE-2026-64314 https://www.cve.org/CVERecord?id=CVE-2026-64314 Référence CVE CVE-2026-64315 https://www.cve.org/CVERecord?id=CVE-2026-64315 Référence CVE CVE-2026-64316 https://www.cve.org/CVERecord?id=CVE-2026-64316 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64318 https://www.cve.org/CVERecord?id=CVE-2026-64318 Référence CVE CVE-2026-64319 https://www.cve.org/CVERecord?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64325 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-64296 Référence CVE CVE-2026-64303 https://www.cve.org/CVERecord?id=CVE-2026-64303 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64305 https://www.cve.org/CVERecord?id=CVE-2026-64305 Référence CVE CVE-2026-64306 https://www.cve.org/CVERecord?id=CVE-2026-64306 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=CVE-2026-64313 Référence CVE CVE-2026-64315 https://www.cve.org/CVERecord?id=CVE-2026-64315 Référence CVE CVE-2026-64316 https://www.cve.org/CVERecord?id=CVE-2026-64316 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64306 Référence CVE CVE-2026-64307 https://www.cve.org/CVERecord?id=CVE-2026-64307 Référence CVE CVE-2026-64308 https://www.cve.org/CVERecord?id=CVE-2026-64308 Référence CVE CVE-2026-64309 https://www.cve.org/CVERecord?id=CVE-2026-64309 Référence CVE CVE-2026-64310 https://www.cve.org/CVERecord?id=CVE-2026-64310 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=CVE-2026-64313 Référence CVE CVE-2026-64315 https://www.cve.org/CVERecord?id=CVE-2026-64315 Référence CVE CVE-2026-64316 https://www.cve.org/CVERecord?id=CVE-2026-64316 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64318 https://www.cve.org/CVERecord?id=CVE-2026-64318 Référence CVE CVE-2026-64319 https://www.cve.org/CVERecord?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64326 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64299 Référence CVE CVE-2026-64301 https://www.cve.org/CVERecord?id=CVE-2026-64301 Référence CVE CVE-2026-64303 https://www.cve.org/CVERecord?id=CVE-2026-64303 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64306 https://www.cve.org/CVERecord?id=CVE-2026-64306 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=CVE-2026-64313 Référence CVE CVE-2026-64315 https://www.cve.org/CVERecord?id=CVE-2026-64315 Référence CVE CVE-2026-64316 https://www.cve.org/CVERecord?id=CVE-2026-64316 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64318 https://www.cve.org/CVERecord?id=CVE-2026-64318 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-032050LinuxのLinux Kernelにおける境界外読み取りに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。isofsのRock Ridgeにおけるシンボリックリンク（SL）コンポーネントをSLレコード内に拘束する処置が行われました。get_symlink_chunk()関数およびparse_rock_ridge_inode_internal()関数内のSL処理は、Rock Ridgeの"SL"（シンボリックリンク）レコードの可変長コンポーネントを順に読み進めます。各コンポーネントは2バイトのヘッダー（flags, len）とlenバイトのテキストで構成されており、合計でslp-＞len + 2バイトを占めます。両ループはslp-＞lenを読み取り次のコンポーネントに進みますが、get_symlink_chunk()関数はさらにmemcpy(rpnt, slp-＞text, slp-＞len)を実行します。しかし、いずれの関数もコンポーネントがSLレコード内に存在するかを参照前に検証していません。細工されたSLレコードのコンポーネントがレコード(rr-＞len)の範囲を超えて長さ(len)を宣言している場合、最大255バイトの範囲外読み取りが発生する可能性があります。例えば、レコードが小さなkmalloc()で割り当てられた継続ブロックの末尾にある場合（CEレコード経由で辿られる場合など）、読み取りは割り当て領域を越えて行われます。get_symlink_chunk()関数は読み取り済みの範囲外のバイトをreadlink()によりユーザ空間に返すシンボリックリンク本体にコピーしてしまい、隣接するカーネルメモリを漏洩させる恐れがあります。ISO 9660イメージは信頼できないリムーバブルメディアから日常的にマウントされており、デスクトップ環境はCAP_SYS_ADMIN権限なしで自動マウント（例: udisks2経由）を行うため、レコード内容は攻撃者によって制御される可能性があります。レコード内の残りのバイト数に収まらないコンポーネントは利用前に拒否されます。get_symlink_chunk()関数では既存の出力バッファ(plimit)チェックと同様にNULLを返し、不正なレコードの場合はreadlink()が-EIOエラーで失敗するように処理します。parse_rock_ridge_inode_internal()関数ではinodeのサイズ内で走査を停止するように改善されています。

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.12, 5.10.261 ≤ 5.10.*, 5.15.212 ≤ 5.15.*, 6.1.178 ≤ 6.1.*, 6.6.145 ≤ 6.6.*, 6.12.96 ≤ 6.12.*, 6.18.39 ≤ 6.18.*, 7.1.4 ≤ 7.1.*, 7.2 ≤ *
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 25 Jul 2026 · Last source change 8 Sept 2026, 08:50 UTC · CWE-125 · Out-of-bounds Read

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

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 1015e1c4b2fadd9c09704e24738e46598778c869; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 36fe7d25dbc40da0c6b1dd4513a4f69ac6164eee; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < a22cb6bb54dc167047ea9e70d97dfbc2c15649e3; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b736b12108fd116c41777628f5a333791604df26; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6bf41db09ef935d76fcc84ccf213b42c18de95ee; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b5699642640d6cff357638738c5293985cd5a53d; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 9830725078c8483c6831ec10222ae724806ea36b; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5fa1d6a5ec2356d2107dead614437c66fa7138b1 · Fixed: < 2.6.12; 5.10.261 ≤ 5.10.*; 5.15.212 ≤ 5.15.*; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.96 ≤ 6.12.*; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*
    After
    Linux: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 1015e1c4b2fadd9c09704e24738e46598778c869, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 36fe7d25dbc40da0c6b1dd4513a4f69ac6164eee, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < a22cb6bb54dc167047ea9e70d97dfbc2c15649e3, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b736b12108fd116c41777628f5a333791604df26, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6bf41db09ef935d76fcc84ccf213b42c18de95ee, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b5699642640d6cff357638738c5293985cd5a53d, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 9830725078c8483c6831ec10222ae724806ea36b, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5fa1d6a5ec2356d2107dead614437c66fa7138b1, 2.6.12 · Fixed: Linux: < 2.6.12, 5.10.261 ≤ 5.10.*, 5.15.212 ≤ 5.15.*, 6.1.178 ≤ 6.1.*, 6.6.145 ≤ 6.6.*, 6.12.96 ≤ 6.12.*, 6.18.39 ≤ 6.18.*, 7.1.4 ≤ 7.1.*, 7.2 ≤ *
    CNA ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added patch: git.kernel.org/1015e1c4b2fadd9c09704e24738e46598778c869; added patch: git.kernel.org/36fe7d25dbc40da0c6b1dd4513a4f69ac6164eee; 6 further additions.
    Before
    remediation: git.kernel.org/1015e1c4b2fadd9c09704e24738e46598778c869
    After
    patch: git.kernel.org/1015e1c4b2fadd9c09704e24738e46598778c869 · patch: git.kernel.org/36fe7d25dbc40da0c6b1dd4513a4f69ac6164eee · patch: git.kernel.org/5fa1d6a5ec2356d2107dead614437c66fa7138b1 · 6 more references
    git.kernel.org ↗
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-49029↗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-64317 · cve.blacktree.nl