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

usb: typec: tcpm: Validate SVID index in svdm_consume_modes()

Linux · Linux

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 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 17 Aug 2026

Evidence used

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

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

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

1 current
CVE-2026-64330 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-64330
238 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: Validate SVID index in svdm_consume_modes() In svdm_consume_modes(), the SVID value is read from pmdata->svids using pmdata->svid_index as an array index without bounds validation: paltmode->svid = pmdata->svids[pmdata->svid_index]; If pmdata->svid_index is driven beyond SVID_DISCOVERY_MAX (16), it results in an out-of-bounds read of the pmdata->svids array. Because pd_mode_data is embedded inside struct tcpm_port, indexing past svids reads into adjacent fields. In particular: - At index 16, it reads the altmodes count. - At index 18 and beyond, it reads into altmode_desc[], which contains partner-supplied SVDM Discovery Modes VDOs. By injecting a chosen SVID into altmode_desc[0].vdo and driving svid_index to 20, the partner can force paltmode->svid to be loaded with an arbitrary, partner- chosen SVID, which is then registered via typec_partner_register_altmode(). Fix this by validating that pmdata->svid_index is non-negative and strictly less than pmdata->nsvids before accessing the pmdata->svids array inside svdm_consume_modes().
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2026-48874

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 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: usb: typec: tcpm: Validate SVID index in svdm_consume_modes() In svdm_consume_modes(), the SVID value is read from pmdata->svids using pmdata->svid_index as an array index without bounds validation: paltmode->svid = pmdata->svids[pmdata->svid_index]; If pmdata->svid_index is driven beyond SVID_DISCOVERY_MAX (16), it results in an out-of-bounds read of the pmdata->svids array. Because pd_mode_data is embedded inside struct tcpm_port, indexing past svids reads into adjacent fields. In particular: - At index 16, it reads the altmodes count. - At index 18 and beyond, it reads into altmode_desc[], which contains partner-supplied SVDM Discovery Modes VDOs. By injecting a chosen SVID into altmode_desc[0].vdo and driving svid_index to 20, the partner can force paltmode->svid to be loaded with an arbitrary, partner- chosen SVID, which is then registered via typec_partner_register_altmode(). Fix this by validating that pmdata->svid_index is non-negative and strictly less than pmdata->nsvids before accessing the pmdata->svids array inside svdm_consume_modes().

What

In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: Validate SVID index in svdm_consume_modes() In svdm_consume_modes(), the SVID value is read from pmdata->svids using pmdata->svid_index as an array index without bounds validation: paltmode->svid = pmdata->svids[pmdata->svid_index]; If pmdata->svid_index is driven beyond SVID_DISCOVERY_MAX (16), it results in an out-of-bounds read of the pmdata->svids array. Because pd_mode_data is embedded inside struct tcpm_port, indexing past svids reads into adjacent fields. In particular: - At index 16, it reads the altmodes count. - At index 18 and beyond, it reads into altmode_desc[], which contains partner-supplied SVDM Discovery Modes VDOs. By injecting a chosen SVID into altmode_desc[0].vdo and driving svid_index to 20, the partner can force paltmode->svid to be loaded with an arbitrary, partner- chosen SVID, which is then registered via typec_partner_register_altmode(). Fix this by validating that pmdata->svid_index is non-negative and strictly less than pmdata->nsvids before accessing the pmdata->svids array inside svdm_consume_modes().

Why

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

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: usb: typec: tcpm: Validate SVID index in svdm_consume_modes() In svdm_consume_modes(), the SVID value is read from pmdata->svids using pmdata->svid_index as an array index without bounds validation: paltmode->svid = pmdata->svids[pmdata->svid_index]; If pmdata->svid_index is driven beyond SVID_DISCOVERY_MAX (16), it results in an out-of-bounds read of the pmdata->svids array. Because pd_mode_data is embedded inside struct tcpm_port, indexing past svids reads into adjacent fields. In particular: - At index 16, it reads the altmodes count. - At index 18 and beyond, it reads into altmode_desc[], which contains partner-supplied SVDM Discovery Modes VDOs. By injecting a chosen SVID into altmode_desc[0].vdo and driving svid_index to 20, the partner can force paltmode->svid to be loaded with an arbitrary, partner- chosen SVID, which is then registered via typec_partner_register_altmode(). Fix this by validating that pmdata->svid_index is non-negative and strictly less than pmdata->nsvids before accessing the pmdata->svids array inside svdm_consume_modes().

Why

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

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 → Improper Validation of Array Index → 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-129 ↗

CWE-129: Improper Validation of Array Index. The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

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

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

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

Official authority intelligence

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

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-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=CVE-2026-64325 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=CVE-2026-64328 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=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=CVE-2026-64335 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64337 https://www.cve.org/CVERecord?id=CVE-2026-64337 Référence CVE CVE-2026-64338 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-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=CVE-2026-64325 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=CVE-2026-64328 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=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=CVE-2026-64335 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64337 https://www.cve.org/CVERecord?id=CVE-2026-64337 Référence CVE CVE-2026-64338 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-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=CVE-2026-64325 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=CVE-2026-64328 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=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=CVE-2026-64335 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64337 https://www.cve.org/CVERecord?id=CVE-2026-64337 Référence CVE CVE-2026-64338 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-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=CVE-2026-64325 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=CVE-2026-64328 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=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=CVE-2026-64335 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64337 https://www.cve.org/CVERecord?id=CVE-2026-64337 Référence CVE CVE-2026-64338 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64223 https://www.cve.org/CVERecord?id=CVE-2026-64223 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64242 https://www.cve.org/CVERecord?id=CVE-2026-64242 Référence CVE CVE-2026-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64345 https://www.cve.org/CVERecord?id=CVE-2026-64345 Référence CVE CVE-2026-64347 https://www.cve.org/CVERecord?id=CVE-2026-64347 Référence CVE CVE-2026-64465 https://www.cve.org/CVERecord?id=CVE-2026-64465 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64560 https://www.cve.org/CVERecord?id=CVE-2026-64560 Référence CVE CVE-2026-64561 https://www.cve.org/CVERecord?id=CVE-2026-64561 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64191 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64223 https://www.cve.org/CVERecord?id=CVE-2026-64223 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64233 https://www.cve.org/CVERecord?id=CVE-2026-64233 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64241 https://www.cve.org/CVERecord?id=CVE-2026-64241 Référence CVE CVE-2026-64242 https://www.cve.org/CVERecord?id=CVE-2026-64242 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64345 https://www.cve.org/CVERecord?id=CVE-2026-64345 Référence CVE CVE-2026-64347 https://www.cve.org/CVERecord?id=CVE-2026-64347 Référence CVE CVE-2026-64357 https://www.cve.org/CVERecord?id=CVE-2026-64357 Référence CVE CVE-2026-64465 https://www.cve.org/CVERecord?id=CVE-2026-64465 Référence CVE CVE-2026-64528 https://www.cve.org/CVERecord?id=CVE-2026-64528 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64560 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-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=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=CVE-2026-64328 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=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=CVE-2026-64335 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64337 https://www.cve.org/CVERecord?id=CVE-2026-64337 Référence CVE CVE-2026-64338 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-63958 Référence CVE CVE-2026-63968 https://www.cve.org/CVERecord?id=CVE-2026-63968 Référence CVE CVE-2026-63971 https://www.cve.org/CVERecord?id=CVE-2026-63971 Référence CVE CVE-2026-63975 https://www.cve.org/CVERecord?id=CVE-2026-63975 Référence CVE CVE-2026-63984 https://www.cve.org/CVERecord?id=CVE-2026-63984 Référence CVE CVE-2026-63994 https://www.cve.org/CVERecord?id=CVE-2026-63994 Référence CVE CVE-2026-64106 https://www.cve.org/CVERecord?id=CVE-2026-64106 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64465 https://www.cve.org/CVERecord?id=CVE-2026-64465 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64560 https://www.cve.org/CVERecord?id=CVE-2026-64560 Référence CVE CVE-2026-64561 https://www.cve.org/CVERecord?id=CVE-2026-64561 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=CVE-2026-64564 Référence CVE CVE-2026-64600 https://www.cve.org/CVERecord?id=CVE-2026-64600 Gestion détaillée du document le 14 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À

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

d?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=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=CVE-2026-64335 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64337 https://www.cve.org/CVERecord?id=CVE-2026-64337 Référence CVE CVE-2026-64338 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: < 4.19, 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 17 Aug 2026, 04:53 UTC · CWE-129 · Improper Validation of Array Index

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

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added patch: git.kernel.org/012406f89abc52d1d5f07aa5653b519ebf6d2407; added patch: git.kernel.org/313ca06e7e224ca1dfadd5722fe71fb8bc276b8b; 6 further additions.
    Before
    remediation: git.kernel.org/89ff289cbf5d3b659a2babc5ccaae4eaf7e7cf53
    After
    patch: git.kernel.org/012406f89abc52d1d5f07aa5653b519ebf6d2407 · patch: git.kernel.org/313ca06e7e224ca1dfadd5722fe71fb8bc276b8b · patch: git.kernel.org/3e1b1ac47e8163627f159f30d80d51b914620dd4 · 6 more references
    git.kernel.org ↗
  2. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    NIST NVD ↗
  3. CVSS scoreCVSS score changed from not recorded to 7.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    7.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
    NIST NVD ↗
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-48874↗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-64330 · cve.blacktree.nl