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

i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock

Linux · Linux

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

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

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.22% for the current model date.

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 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.105-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-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.107-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.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.8-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-74463 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock
274 known not affected

The vendor explicitly states that these products are not 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 i2c: jz4780 driver. A severe deadlock can occur between the Common Clock Framework (CCF) and the I2C adapter lock. This happens when an I2C-controlled clock generator client is registered or modified, and a concurrent I2C transfer attempts to acquire a lock already held, creating a circular dependency. This vulnerability can lead to a system freeze, resulting in a Denial of Service (DoS).
Remediation
No remediation text is recorded.
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-59656

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock Fix a severe AB/BA deadlock between the Common Clock Framework (CCF) and the I2C adapter lock, which triggers when an I2C-controlled clock generator client (like the Si5351) is registered or modified under the CCF. During an i2c client clock (generator) frequency change, the CCF acquires its global 'prepare_lock' mutex and the driver calls i2c_transfer() to update the client's chip registers, stalling for the adapter's I2C bus lock. Concurrently, an independent, parallel transfer on the same bus (e.g., a GPIO expander handling LEDs) can hold the I2C adapter lock. Inside this parallel transfer path, jz4780_i2c_set_speed() calls clk_get_rate() on the host controller's input clock to calculate bus timings. This call attempts to acquire the blocked CCF 'prepare_lock', creating a circular dependency that freezes the system. The jz4780 host controller clock itself is static and never changes at runtime. However, calling clk_get_rate() inside the active transfer path introduces an unnecessary dependency on the CCF internal locks. Eliminate this synchronous clk_get_rate() call from the active transfer path by caching the static host peripheral clock rate once - inside the private jz4780_i2c structure during jz4780_i2c_probe(). Update jz4780_i2c_set_speed() to use this cached value, safely decoupling active I2C transactions from the CCF internal locks without any risk of stale timings. Assisted-by web based Google AI (pinpointing the bug and writing the message).

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

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 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: i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock Fix a severe AB/BA deadlock between the Common Clock Framework (CCF) and the I2C adapter lock, which triggers when an I2C-controlled clock generator client (like the Si5351) is registered or modified under the CCF. During an i2c client clock (generator) frequency change, the CCF acquires its global 'prepare_lock' mutex and the driver calls i2c_transfer() to update the client's chip registers, stalling for the adapter's I2C bus lock. Concurrently, an independent, parallel transfer on the same bus (e.g., a GPIO expander handling LEDs) can hold the I2C adapter lock. Inside this parallel transfer path, jz4780_i2c_set_speed() calls clk_get_rate() on the host controller's input clock to calculate bus timings. This call attempts to acquire the blocked CCF 'prepare_lock', creating a circular dependency that freezes the system. The jz4780 host controller clock itself is static and never changes at runtime. However, calling clk_get_rate() inside the active transfer path introduces an unnecessary dependency on the CCF internal locks. Eliminate this synchronous clk_get_rate() call from the active transfer path by caching the static host peripheral clock rate once - inside the private jz4780_i2c structure during jz4780_i2c_probe(). Update jz4780_i2c_set_speed() to use this cached value, safely decoupling active I2C transactions from the CCF internal locks without any risk of stale timings. Assisted-by web based Google AI (pinpointing the bug and writing the message).

What

In the Linux kernel, the following vulnerability has been resolved: i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock Fix a severe AB/BA deadlock between the Common Clock Framework (CCF) and the I2C adapter lock, which triggers when an I2C-controlled clock generator client (like the Si5351) is registered or modified under the CCF. During an i2c client clock (generator) frequency change, the CCF acquires its global 'prepare_lock' mutex and the driver calls i2c_transfer() to update the client's chip registers, stalling for the adapter's I2C bus lock. Concurrently, an independent, parallel transfer on the same bus (e.g., a GPIO expander handling LEDs) can hold the I2C adapter lock. Inside this parallel transfer path, jz4780_i2c_set_speed() calls clk_get_rate() on the host controller's input clock to calculate bus timings. This call attempts to acquire the blocked CCF 'prepare_lock', creating a circular dependency that freezes the system. The jz4780 host controller clock itself is static and never changes at runtime. However, calling clk_get_rate() inside the active transfer path introduces an unnecessary dependency on the CCF internal locks. Eliminate this synchronous clk_get_rate() call from the active transfer path by caching the static host peripheral clock rate once - inside the private jz4780_i2c structure during jz4780_i2c_probe(). Update jz4780_i2c_set_speed() to use this cached value, safely decoupling active I2C transactions from the CCF internal locks without any risk of stale timings. Assisted-by web based Google AI (pinpointing the bug and writing the message).

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock Fix a severe AB/BA deadlock between the Common Clock Framework (CCF) and the I2C adapter lock, which triggers when an I2C-controlled clock generator client (like the Si5351) is registered or modified under the CCF. During an i2c client clock (generator) frequency change, the CCF acquires its global 'prepare_lock' mutex and the driver calls i2c_transfer() to update the client's chip registers, stalling for the adapter's I2C bus lock. Concurrently, an independent, parallel transfer on the same bus (e.g., a GPIO expander handling LEDs) can hold the I2C adapter lock. Inside this parallel transfer path, jz4780_i2c_set_speed() calls clk_get_rate() on the host controller's input clock to calculate bus timings. This call attempts to acquire the blocked CCF 'prepare_lock', creating a circular dependency that freezes the system. The jz4780 host controller clock itself is static and never changes at runtime. However, calling clk_get_rate() inside the active transfer path introduces an unnecessary dependency on the CCF internal locks. Eliminate this synchronous clk_get_rate() call from the active transfer path by caching the static host peripheral clock rate once - inside the private jz4780_i2c structure during jz4780_i2c_probe(). Update jz4780_i2c_set_speed() to use this cached value, safely decoupling active I2C transactions from the CCF internal locks without any risk of stale timings. Assisted-by web based Google AI (pinpointing the bug and writing the message).

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
the affected interface → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
Not available from the selected scoring authority.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-59656Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock Fix a severe AB/BA deadlock between the Common Clock Framework (CCF) and the I2C adapter lock, which triggers when an I2C-controlled clock generator client (like the Si5351) is registered or modified under the CCF. During an i2c client clock (generator) frequency change, the CCF acquires its global 'prepare_lock' mutex and the driver calls i2c_transfer() to update the client's chip registers, stalling for the adapter's I2C bus lock. Concurrently, an independent, parallel transfer on the same bus (e.g., a GPIO expander handling LEDs) can hold the I2C adapter lock. Inside this parallel transfer path, jz4780_i2c_set_speed() calls clk_get_rate() on the host controller's input clock to calculate bus timings. This call attempts to acquire the blocked CCF 'prepare_lock', creating a circular dependency that freezes the system. The jz4780 host controller clock itself is static and never changes at runtime. However, calling clk_get_rate() inside the active transfer path introduces an unnecessary dependency on the CCF internal locks. Eliminate this synchronous clk_get_rate() call from the active transfer path by caching the static host peripheral clock rate once - inside the private jz4780_i2c structure during jz4780_i2c_probe(). Update jz4780_i2c_set_speed() to use this cached value, safely decoupling active I2C transactions from the CCF internal locks without any risk of stale timings. Assisted-by web based Google AI (pinpointing the bug and writing the message).

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

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.

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

d?id=CVE-2026-74453 Référence CVE CVE-2026-74454 https://www.cve.org/CVERecord?id=CVE-2026-74454 Référence CVE CVE-2026-74455 https://www.cve.org/CVERecord?id=CVE-2026-74455 Référence CVE CVE-2026-74456 https://www.cve.org/CVERecord?id=CVE-2026-74456 Référence CVE CVE-2026-74457 https://www.cve.org/CVERecord?id=CVE-2026-74457 Référence CVE CVE-2026-74458 https://www.cve.org/CVERecord?id=CVE-2026-74458 Référence CVE CVE-2026-74459 https://www.cve.org/CVERecord?id=CVE-2026-74459 Référence CVE CVE-2026-74460 https://www.cve.org/CVERecord?id=CVE-2026-74460 Référence CVE CVE-2026-74461 https://www.cve.org/CVERecord?id=CVE-2026-74461 Référence CVE CVE-2026-74463 https://www.cve.org/CVERecord?id=CVE-2026-74463 Référence CVE CVE-2026-74464 https://www.cve.org/CVERecord?id=CVE-2026-74464 Référence CVE CVE-2026-74465 https://www.cve.org/CVERecord?id=CVE-2026-74465 Référence CVE CVE-2026-74467 https://www.cve.org/CVERecord?id=CVE-2026-74467 Référence CVE CVE-2026-74468 https://www.cve.org/CVERecord?id=CVE-2026-74468 Référence CVE CVE-2026-74469 https://www.cve.org/CVERecord?id=CVE-2026-74469 Référence CVE CVE-2026-74470 https://www.cve.org/CVERecord?id=CVE-2026-74470 Référence CVE CVE-2026-74471 https://www.cve.org/CVERecord?id=CVE-2026-74471 Référence CVE CVE-2026-74472 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-74453 Référence CVE CVE-2026-74454 https://www.cve.org/CVERecord?id=CVE-2026-74454 Référence CVE CVE-2026-74455 https://www.cve.org/CVERecord?id=CVE-2026-74455 Référence CVE CVE-2026-74456 https://www.cve.org/CVERecord?id=CVE-2026-74456 Référence CVE CVE-2026-74457 https://www.cve.org/CVERecord?id=CVE-2026-74457 Référence CVE CVE-2026-74458 https://www.cve.org/CVERecord?id=CVE-2026-74458 Référence CVE CVE-2026-74459 https://www.cve.org/CVERecord?id=CVE-2026-74459 Référence CVE CVE-2026-74460 https://www.cve.org/CVERecord?id=CVE-2026-74460 Référence CVE CVE-2026-74461 https://www.cve.org/CVERecord?id=CVE-2026-74461 Référence CVE CVE-2026-74463 https://www.cve.org/CVERecord?id=CVE-2026-74463 Référence CVE CVE-2026-74464 https://www.cve.org/CVERecord?id=CVE-2026-74464 Référence CVE CVE-2026-74465 https://www.cve.org/CVERecord?id=CVE-2026-74465 Référence CVE CVE-2026-74467 https://www.cve.org/CVERecord?id=CVE-2026-74467 Référence CVE CVE-2026-74468 https://www.cve.org/CVERecord?id=CVE-2026-74468 Référence CVE CVE-2026-74469 https://www.cve.org/CVERecord?id=CVE-2026-74469 Référence CVE CVE-2026-74470 https://www.cve.org/CVERecord?id=CVE-2026-74470 Référence CVE CVE-2026-74471 https://www.cve.org/CVERecord?id=CVE-2026-74471 Référence CVE CVE-2026-74472 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-74453 Référence CVE CVE-2026-74454 https://www.cve.org/CVERecord?id=CVE-2026-74454 Référence CVE CVE-2026-74455 https://www.cve.org/CVERecord?id=CVE-2026-74455 Référence CVE CVE-2026-74456 https://www.cve.org/CVERecord?id=CVE-2026-74456 Référence CVE CVE-2026-74457 https://www.cve.org/CVERecord?id=CVE-2026-74457 Référence CVE CVE-2026-74458 https://www.cve.org/CVERecord?id=CVE-2026-74458 Référence CVE CVE-2026-74459 https://www.cve.org/CVERecord?id=CVE-2026-74459 Référence CVE CVE-2026-74460 https://www.cve.org/CVERecord?id=CVE-2026-74460 Référence CVE CVE-2026-74461 https://www.cve.org/CVERecord?id=CVE-2026-74461 Référence CVE CVE-2026-74463 https://www.cve.org/CVERecord?id=CVE-2026-74463 Référence CVE CVE-2026-74464 https://www.cve.org/CVERecord?id=CVE-2026-74464 Référence CVE CVE-2026-74465 https://www.cve.org/CVERecord?id=CVE-2026-74465 Référence CVE CVE-2026-74467 https://www.cve.org/CVERecord?id=CVE-2026-74467 Référence CVE CVE-2026-74468 https://www.cve.org/CVERecord?id=CVE-2026-74468 Référence CVE CVE-2026-74469 https://www.cve.org/CVERecord?id=CVE-2026-74469 Référence CVE CVE-2026-74470 https://www.cve.org/CVERecord?id=CVE-2026-74470 Référence CVE CVE-2026-74471 https://www.cve.org/CVERecord?id=CVE-2026-74471 Référence CVE CVE-2026-74472 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
Linux: ba92222ed63a12d09120df9b92f56cc990abac19 < cc111696ef420f6bb552b2526530067977f0b406, ba92222ed63a12d09120df9b92f56cc990abac19 < f96a719d9f8a797105ec5cacf568ab128e33391f, ba92222ed63a12d09120df9b92f56cc990abac19 < deffad5bb4f8b4f09e46252f24754ddc9960b244, ba92222ed63a12d09120df9b92f56cc990abac19 < 14429dc1c756c35e106f01ff09cadccb82f5531d, ba92222ed63a12d09120df9b92f56cc990abac19 < b6cb47e186abba85a3b08aa3023067ab82577286, ba92222ed63a12d09120df9b92f56cc990abac19 < 19b783335d62e7a2367436a6e1f1b37da1878360, ba92222ed63a12d09120df9b92f56cc990abac19 < aa1944b52d6492c48bdd17046578aa0d953546e6, ba92222ed63a12d09120df9b92f56cc990abac19 < d99607c888f26e8a4e9fe9772860cef4aff86bb4, 4.1
Fixed
Linux: < 4.1, 5.10.265 ≤ 5.10.*, 5.15.216 ≤ 5.15.*, 6.1.183 ≤ 6.1.*, 6.6.151 ≤ 6.6.*, 6.12.103 ≤ 6.12.*, 6.18.44 ≤ 6.18.*, 7.1.8 ≤ 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 15 Aug 2026 · Last source change 19 Aug 2026, 16:37 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceUnavailable
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-23
European sourceENISA EUVD · EUVD-2026-59656
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD received

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/cc111696ef420f6bb552b2526530067977f0b406; removed remediation: git.kernel.org/14429dc1c756c35e106f01ff09cadccb82f5531d.
    Before
    remediation: git.kernel.org/14429dc1c756c35e106f01ff09cadccb82f5531d
    After
    remediation: git.kernel.org/cc111696ef420f6bb552b2526530067977f0b406
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    ba92222ed63a12d09120df9b92f56cc990abac19 < 14429dc1c756c35e106f01ff09cadccb82f5531d; ba92222ed63a12d09120df9b92f56cc990abac19 < b6cb47e186abba85a3b08aa3023067ab82577286; ba92222ed63a12d09120df9b92f56cc990abac19 < 19b783335d62e7a2367436a6e1f1b37da1878360; ba92222ed63a12d09120df9b92f56cc990abac19 < aa1944b52d6492c48bdd17046578aa0d953546e6; ba92222ed63a12d09120df9b92f56cc990abac19 < d99607c888f26e8a4e9fe9772860cef4aff86bb4; 4.1 · Fixed: < 4.1; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    After
    ba92222ed63a12d09120df9b92f56cc990abac19 < cc111696ef420f6bb552b2526530067977f0b406; ba92222ed63a12d09120df9b92f56cc990abac19 < f96a719d9f8a797105ec5cacf568ab128e33391f; ba92222ed63a12d09120df9b92f56cc990abac19 < deffad5bb4f8b4f09e46252f24754ddc9960b244; ba92222ed63a12d09120df9b92f56cc990abac19 < 14429dc1c756c35e106f01ff09cadccb82f5531d; ba92222ed63a12d09120df9b92f56cc990abac19 < b6cb47e186abba85a3b08aa3023067ab82577286; ba92222ed63a12d09120df9b92f56cc990abac19 < 19b783335d62e7a2367436a6e1f1b37da1878360; ba92222ed63a12d09120df9b92f56cc990abac19 < aa1944b52d6492c48bdd17046578aa0d953546e6; ba92222ed63a12d09120df9b92f56cc990abac19 < d99607c888f26e8a4e9fe9772860cef4aff86bb4 · Fixed: < 4.1; 5.10.265 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    ba92222ed63a12d09120df9b92f56cc990abac19 < 14429dc1c756c35e106f01ff09cadccb82f5531d; ba92222ed63a12d09120df9b92f56cc990abac19 < b6cb47e186abba85a3b08aa3023067ab82577286; ba92222ed63a12d09120df9b92f56cc990abac19 < 19b783335d62e7a2367436a6e1f1b37da1878360; ba92222ed63a12d09120df9b92f56cc990abac19 < aa1944b52d6492c48bdd17046578aa0d953546e6; ba92222ed63a12d09120df9b92f56cc990abac19 < d99607c888f26e8a4e9fe9772860cef4aff86bb4; 4.1 · Fixed: < 4.1; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2-rc6 ≤ *
    After
    ba92222ed63a12d09120df9b92f56cc990abac19 < 14429dc1c756c35e106f01ff09cadccb82f5531d; ba92222ed63a12d09120df9b92f56cc990abac19 < b6cb47e186abba85a3b08aa3023067ab82577286; ba92222ed63a12d09120df9b92f56cc990abac19 < 19b783335d62e7a2367436a6e1f1b37da1878360; ba92222ed63a12d09120df9b92f56cc990abac19 < aa1944b52d6492c48bdd17046578aa0d953546e6; ba92222ed63a12d09120df9b92f56cc990abac19 < d99607c888f26e8a4e9fe9772860cef4aff86bb4; 4.1 · Fixed: < 4.1; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  4. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-59656↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-74463 · cve.blacktree.nl