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

Input: elan_i2c - prevent division by zero and arithmetic underflow

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 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.16% for the current model date.

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 121 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 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.180-1Debian Security Tracker ↗Source updated 6 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 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-64275 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-64275
294 known affected

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

  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: Input: elan_i2c - prevent division by zero and arithmetic underflow The Elan I2C touchpad driver queries the device for its physical dimensions and trace counts to calculate the device resolution and width. However, if the device firmware or device tree provides invalid zero values for x_traces or y_traces, it results in a fatal division-by-zero exception leading to a kernel panic during device probe. Add checks to ensure these parameters are non-zero before performing the division. If invalid trace values are detected, fall back to a safe default of 1. Additionally, prevent an arithmetic underflow in the touch reporting logic. Previously, if the calculated or fallback width was smaller than ETP_FWIDTH_REDUCE (90), the subtraction would underflow, resulting in a massive unsigned integer being reported to userspace. Clamp the adjusted width to a minimum of 0 to safely handle small physical dimensions and fallback scenarios. Completing the probe with safe fallback values ensures the sysfs nodes are created, keeping the firmware update path intact so a recovery firmware can be flashed to the device.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64275 · CSAF 2.0 · revision 3 · status not statedRed Hat Product Securitykernel: Input: elan_i2c - prevent division by zero and arithmetic underflow
101 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's Elan I2C touchpad driver. This vulnerability occurs when the driver receives invalid zero values for touchpad dimensions from device firmware or the device tree, or when a calculated width is too small. A local attacker with control over device input or a malicious device could exploit this to trigger a division-by-zero error, leading to a kernel panic and a denial of service.
Remediation
Fix deferred
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-48987

No EUVD known-exploited evidence

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

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 121 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: Input: elan_i2c - prevent division by zero and arithmetic underflow The Elan I2C touchpad driver queries the device for its physical dimensions and trace counts to calculate the device resolution and width. However, if the device firmware or device tree provides invalid zero values for x_traces or y_traces, it results in a fatal division-by-zero exception leading to a kernel panic during device probe. Add checks to ensure these parameters are non-zero before performing the division. If invalid trace values are detected, fall back to a safe default of 1. Additionally, prevent an arithmetic underflow in the touch reporting logic. Previously, if the calculated or fallback width was smaller than ETP_FWIDTH_REDUCE (90), the subtraction would underflow, resulting in a massive unsigned integer being reported to userspace. Clamp the adjusted width to a minimum of 0 to safely handle small physical dimensions and fallback scenarios. Completing the probe with safe fallback values ensures the sysfs nodes are created, keeping the firmware update path intact so a recovery firmware can be flashed to the device.

What

In the Linux kernel, the following vulnerability has been resolved: Input: elan_i2c - prevent division by zero and arithmetic underflow The Elan I2C touchpad driver queries the device for its physical dimensions and trace counts to calculate the device resolution and width. However, if the device firmware or device tree provides invalid zero values for x_traces or y_traces, it results in a fatal division-by-zero exception leading to a kernel panic during device probe. Add checks to ensure these parameters are non-zero before performing the division. If invalid trace values are detected, fall back to a safe default of 1. Additionally, prevent an arithmetic underflow in the touch reporting logic. Previously, if the calculated or fallback width was smaller than ETP_FWIDTH_REDUCE (90), the subtraction would underflow, resulting in a massive unsigned integer being reported to userspace. Clamp the adjusted width to a minimum of 0 to safely handle small physical dimensions and fallback scenarios. Completing the probe with safe fallback values ensures the sysfs nodes are created, keeping the firmware update path intact so a recovery firmware can be flashed to the device.

Why

The product divides a value by zero.

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: Input: elan_i2c - prevent division by zero and arithmetic underflow The Elan I2C touchpad driver queries the device for its physical dimensions and trace counts to calculate the device resolution and width. However, if the device firmware or device tree provides invalid zero values for x_traces or y_traces, it results in a fatal division-by-zero exception leading to a kernel panic during device probe. Add checks to ensure these parameters are non-zero before performing the division. If invalid trace values are detected, fall back to a safe default of 1. Additionally, prevent an arithmetic underflow in the touch reporting logic. Previously, if the calculated or fallback width was smaller than ETP_FWIDTH_REDUCE (90), the subtraction would underflow, resulting in a massive unsigned integer being reported to userspace. Clamp the adjusted width to a minimum of 0 to safely handle small physical dimensions and fallback scenarios. Completing the probe with safe fallback values ensures the sysfs nodes are created, keeping the firmware update path intact so a recovery firmware can be flashed to the device.

Why

The product divides a value by zero.

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 → Divide By Zero → 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-369 ↗

CWE-369: Divide By Zero. The product divides a value by zero.

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.
CWE-369
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-64266 Référence CVE CVE-2026-64267 https://www.cve.org/CVERecord?id=CVE-2026-64267 Référence CVE CVE-2026-64268 https://www.cve.org/CVERecord?id=CVE-2026-64268 Référence CVE CVE-2026-64269 https://www.cve.org/CVERecord?id=CVE-2026-64269 Référence CVE CVE-2026-64270 https://www.cve.org/CVERecord?id=CVE-2026-64270 Référence CVE CVE-2026-64271 https://www.cve.org/CVERecord?id=CVE-2026-64271 Référence CVE CVE-2026-64272 https://www.cve.org/CVERecord?id=CVE-2026-64272 Référence CVE CVE-2026-64273 https://www.cve.org/CVERecord?id=CVE-2026-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64278 https://www.cve.org/CVERecord?id=CVE-2026-64278 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64282 https://www.cve.org/CVERecord?id=CVE-2026-64282 Référence CVE CVE-2026-64283 https://www.cve.org/CVERecord?id=CVE-2026-64283 Référence CVE CVE-2026-64284 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-64265 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-64269 https://www.cve.org/CVERecord?id=CVE-2026-64269 Référence CVE CVE-2026-64270 https://www.cve.org/CVERecord?id=CVE-2026-64270 Référence CVE CVE-2026-64271 https://www.cve.org/CVERecord?id=CVE-2026-64271 Référence CVE CVE-2026-64272 https://www.cve.org/CVERecord?id=CVE-2026-64272 Référence CVE CVE-2026-64273 https://www.cve.org/CVERecord?id=CVE-2026-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64278 https://www.cve.org/CVERecord?id=CVE-2026-64278 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64283 https://www.cve.org/CVERecord?id=CVE-2026-64283 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64294 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-64266 Référence CVE CVE-2026-64267 https://www.cve.org/CVERecord?id=CVE-2026-64267 Référence CVE CVE-2026-64268 https://www.cve.org/CVERecord?id=CVE-2026-64268 Référence CVE CVE-2026-64269 https://www.cve.org/CVERecord?id=CVE-2026-64269 Référence CVE CVE-2026-64270 https://www.cve.org/CVERecord?id=CVE-2026-64270 Référence CVE CVE-2026-64271 https://www.cve.org/CVERecord?id=CVE-2026-64271 Référence CVE CVE-2026-64272 https://www.cve.org/CVERecord?id=CVE-2026-64272 Référence CVE CVE-2026-64273 https://www.cve.org/CVERecord?id=CVE-2026-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64278 https://www.cve.org/CVERecord?id=CVE-2026-64278 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64282 https://www.cve.org/CVERecord?id=CVE-2026-64282 Référence CVE CVE-2026-64283 https://www.cve.org/CVERecord?id=CVE-2026-64283 Référence CVE CVE-2026-64284 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-64247 Référence CVE CVE-2026-64249 https://www.cve.org/CVERecord?id=CVE-2026-64249 Référence CVE CVE-2026-64257 https://www.cve.org/CVERecord?id=CVE-2026-64257 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-64269 https://www.cve.org/CVERecord?id=CVE-2026-64269 Référence CVE CVE-2026-64271 https://www.cve.org/CVERecord?id=CVE-2026-64271 Référence CVE CVE-2026-64273 https://www.cve.org/CVERecord?id=CVE-2026-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64296 https://www.cve.org/CVERecord?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=

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

d?id=CVE-2026-64266 Référence CVE CVE-2026-64267 https://www.cve.org/CVERecord?id=CVE-2026-64267 Référence CVE CVE-2026-64268 https://www.cve.org/CVERecord?id=CVE-2026-64268 Référence CVE CVE-2026-64269 https://www.cve.org/CVERecord?id=CVE-2026-64269 Référence CVE CVE-2026-64270 https://www.cve.org/CVERecord?id=CVE-2026-64270 Référence CVE CVE-2026-64271 https://www.cve.org/CVERecord?id=CVE-2026-64271 Référence CVE CVE-2026-64272 https://www.cve.org/CVERecord?id=CVE-2026-64272 Référence CVE CVE-2026-64273 https://www.cve.org/CVERecord?id=CVE-2026-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64278 https://www.cve.org/CVERecord?id=CVE-2026-64278 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64282 https://www.cve.org/CVERecord?id=CVE-2026-64282 Référence CVE CVE-2026-64283 https://www.cve.org/CVERecord?id=CVE-2026-64283 Référence CVE CVE-2026-64284 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-64266 Référence CVE CVE-2026-64267 https://www.cve.org/CVERecord?id=CVE-2026-64267 Référence CVE CVE-2026-64268 https://www.cve.org/CVERecord?id=CVE-2026-64268 Référence CVE CVE-2026-64269 https://www.cve.org/CVERecord?id=CVE-2026-64269 Référence CVE CVE-2026-64270 https://www.cve.org/CVERecord?id=CVE-2026-64270 Référence CVE CVE-2026-64271 https://www.cve.org/CVERecord?id=CVE-2026-64271 Référence CVE CVE-2026-64272 https://www.cve.org/CVERecord?id=CVE-2026-64272 Référence CVE CVE-2026-64273 https://www.cve.org/CVERecord?id=CVE-2026-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64278 https://www.cve.org/CVERecord?id=CVE-2026-64278 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64282 https://www.cve.org/CVERecord?id=CVE-2026-64282 Référence CVE CVE-2026-64283 https://www.cve.org/CVERecord?id=CVE-2026-64283 Référence CVE CVE-2026-64284 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-64247 Référence CVE CVE-2026-64249 https://www.cve.org/CVERecord?id=CVE-2026-64249 Référence CVE CVE-2026-64257 https://www.cve.org/CVERecord?id=CVE-2026-64257 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-64269 https://www.cve.org/CVERecord?id=CVE-2026-64269 Référence CVE CVE-2026-64271 https://www.cve.org/CVERecord?id=CVE-2026-64271 Référence CVE CVE-2026-64273 https://www.cve.org/CVERecord?id=CVE-2026-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64296 https://www.cve.org/CVERecord?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=

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

d?id=CVE-2026-64265 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-64269 https://www.cve.org/CVERecord?id=CVE-2026-64269 Référence CVE CVE-2026-64270 https://www.cve.org/CVERecord?id=CVE-2026-64270 Référence CVE CVE-2026-64271 https://www.cve.org/CVERecord?id=CVE-2026-64271 Référence CVE CVE-2026-64272 https://www.cve.org/CVERecord?id=CVE-2026-64272 Référence CVE CVE-2026-64273 https://www.cve.org/CVERecord?id=CVE-2026-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64284 https://www.cve.org/CVERecord?id=CVE-2026-64284 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64289 https://www.cve.org/CVERecord?id=CVE-2026-64289 Référence CVE CVE-2026-64294 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-64249 Référence CVE CVE-2026-64250 https://www.cve.org/CVERecord?id=CVE-2026-64250 Référence CVE CVE-2026-64252 https://www.cve.org/CVERecord?id=CVE-2026-64252 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-64269 https://www.cve.org/CVERecord?id=CVE-2026-64269 Référence CVE CVE-2026-64271 https://www.cve.org/CVERecord?id=CVE-2026-64271 Référence CVE CVE-2026-64273 https://www.cve.org/CVERecord?id=CVE-2026-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64296 https://www.cve.org/CVERecord?id=CVE-2026-64296 Référence CVE CVE-2026-64297 https://www.cve.org/CVERecord?id=CVE-2026-64297 Référence CVE CVE-2026-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64299 https://www.cve.org/CVERecord?id=CVE-2026-64299 Référence CVE CVE-2026-64301 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-028232LinuxのLinux Kernelにおけるゼロ除算に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。入力: elan_i2c - ゼロ除算および算術アンダーフローの防止。Elan I2C タッチパッドドライバは、デバイスの物理的寸法やトレース数を問い合わせて、デバイスの解像度と幅を計算します。しかし、デバイスのファームウェアまたはデバイシーツリーが x_traces または y_traces に無効なゼロ値を提供した場合、致命的なゼロ除算例外が発生し、デバイスのプローブ中にカーネルパニックを引き起こします。これらのパラメータがゼロでないことを確認するチェックを追加し、無効なトレース値が検出された場合は安全なデフォルト値1にフォールバックするようにしています。さらに、タッチレポートロジックにおける算術アンダーフローを防止しています。以前は、計算された幅またはフォールバック幅が ETP_FWIDTH_REDUCE (90) より小さい場合、引き算でアンダーフローが発生し、ユーザースペースに非常に大きな符号なし整数が報告されていました。調整後の幅を最小0にクランプすることで、小さい物理寸法やフォールバックシナリオを安全に処理しています。安全なフォールバック値でプローブを完了することで、sysfsノードが作成され、ファームウェア更新パスが維持されるため、リカバリファームウェアをデバイスにフラッシュできるようになります。

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: < 3.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:52 UTC · CWE-369 · Divide By Zero

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-48987
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 ↗

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
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-64275 · cve.blacktree.nl