Full vulnerability report · 2026

CVE-2026-80680High confidence

i2c: amd-mp2: Unregister callback on adapter add failure

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

Operational reassessment

Published severity in operational context

Open reassessment dashboard →

Published severityHighOperational priority:Medium, lowered one band.downgradedsince 29 Aug 2026

Evidence used

No CISA KEV confirmation is currently recorded.
Exploitation requires an existing local or physical foothold with privileges.
EPSS is 0.18% 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

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

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.

Canonical Ubuntu Security: 20 affected package states with no published fix

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 release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.105-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.1.187-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`linux-6.12`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.107-1~deb12u1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`7.1.8-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`7.1.8-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, 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 feed`	Canonical 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-80680 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: i2c: amd-mp2: Unregister callback on adapter add failure

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: amd-mp2` driver. During the registration of an I2C adapter, the driver may store a memory address (pointer) that later becomes invalid if the adapter registration fails. This can lead to the driver attempting to access this invalid memory location (a "stale pointer") during interrupt or system-sleep operations. Such an attempt could cause the system to crash, resulting in a denial of service.
Remediation: No remediation text is recorded.

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

In the Linux kernel, the following vulnerability has been resolved: i2c: amd-mp2: Unregister callback on adapter add failure amd_mp2_register_cb() stores the platform I2C context in the MP2 PCI driver's callback table before the adapter is registered. If i2c_add_adapter() fails, probe returns and devres frees the context, but the PCI driver can still dereference the stale pointer from its IRQ and system-sleep callbacks. Unregister the callback before returning the adapter registration error.

What

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

Why

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

How

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 → vulnerable operation → 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.: CWE not yet assigned
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.

Official authority intelligence

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

ENISA EUVD · EUVD-2026-67556Official EUVD mapping

Official EUVD record ↗

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.

Official advisory ↗

Cyber Security Agency of Singapore · English · CSA-SB-20260902Security Bulletin 2 Sept 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 2 Sept 2026, published on 2 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗

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

d?id=CVE-2026-80583 Référence CVE CVE-2026-80584 https://www.cve.org/CVERecord?id=CVE-2026-80584 Référence CVE CVE-2026-80585 https://www.cve.org/CVERecord?id=CVE-2026-80585 Référence CVE CVE-2026-80586 https://www.cve.org/CVERecord?id=CVE-2026-80586 Référence CVE CVE-2026-80587 https://www.cve.org/CVERecord?id=CVE-2026-80587 Référence CVE CVE-2026-80589 https://www.cve.org/CVERecord?id=CVE-2026-80589 Référence CVE CVE-2026-80590 https://www.cve.org/CVERecord?id=CVE-2026-80590 Référence CVE CVE-2026-80678 https://www.cve.org/CVERecord?id=CVE-2026-80678 Référence CVE CVE-2026-80679 https://www.cve.org/CVERecord?id=CVE-2026-80679 Référence CVE CVE-2026-80680 https://www.cve.org/CVERecord?id=CVE-2026-80680 Référence CVE CVE-2026-80681 https://www.cve.org/CVERecord?id=CVE-2026-80681 Référence CVE CVE-2026-80684 https://www.cve.org/CVERecord?id=CVE-2026-80684 Référence CVE CVE-2026-80686 https://www.cve.org/CVERecord?id=CVE-2026-80686 Référence CVE CVE-2026-80689 https://www.cve.org/CVERecord?id=CVE-2026-80689 Référence CVE CVE-2026-80691 https://www.cve.org/CVERecord?id=CVE-2026-80691 Référence CVE CVE-2026-80694 https://www.cve.org/CVERecord?id=CVE-2026-80694 Référence CVE CVE-2026-80695 https://www.cve.org/CVERecord?id=CVE-2026-80695 Référence CVE CVE-2026-80696 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-80573 Référence CVE CVE-2026-80574 https://www.cve.org/CVERecord?id=CVE-2026-80574 Référence CVE CVE-2026-80583 https://www.cve.org/CVERecord?id=CVE-2026-80583 Référence CVE CVE-2026-80584 https://www.cve.org/CVERecord?id=CVE-2026-80584 Référence CVE CVE-2026-80586 https://www.cve.org/CVERecord?id=CVE-2026-80586 Référence CVE CVE-2026-80589 https://www.cve.org/CVERecord?id=CVE-2026-80589 Référence CVE CVE-2026-80590 https://www.cve.org/CVERecord?id=CVE-2026-80590 Référence CVE CVE-2026-80678 https://www.cve.org/CVERecord?id=CVE-2026-80678 Référence CVE CVE-2026-80679 https://www.cve.org/CVERecord?id=CVE-2026-80679 Référence CVE CVE-2026-80680 https://www.cve.org/CVERecord?id=CVE-2026-80680 Référence CVE CVE-2026-80681 https://www.cve.org/CVERecord?id=CVE-2026-80681 Référence CVE CVE-2026-80684 https://www.cve.org/CVERecord?id=CVE-2026-80684 Référence CVE CVE-2026-80686 https://www.cve.org/CVERecord?id=CVE-2026-80686 Référence CVE CVE-2026-80706 https://www.cve.org/CVERecord?id=CVE-2026-80706 Référence CVE CVE-2026-80707 https://www.cve.org/CVERecord?id=CVE-2026-80707 Référence CVE CVE-2026-80708 https://www.cve.org/CVERecord?id=CVE-2026-80708 Référence CVE CVE-2026-80709 https://www.cve.org/CVERecord?id=CVE-2026-80709 Référence CVE CVE-2026-80714 https://www.cve.org/CVERecord?id=

Official advisory ↗

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: 529766e0a0114438887382a68d97341fbf8349fb < 9142a3dcff0d80a3a24ce159aee19ddc869d9784, 529766e0a0114438887382a68d97341fbf8349fb < 2f7789b3a9628819ebf90bcba8f9da3c139f8687, 529766e0a0114438887382a68d97341fbf8349fb < 4786d4d70dcd1e6b7e044f2348e00f201947b69c, 529766e0a0114438887382a68d97341fbf8349fb < b7c2c5c8868737926410b93d1223ada17625ead3, 529766e0a0114438887382a68d97341fbf8349fb < cf107c5983dc70fcf932a305581a5f976d908ff1, 529766e0a0114438887382a68d97341fbf8349fb < 1883a09a37fed497b9efacf736c23624a472246b, 529766e0a0114438887382a68d97341fbf8349fb < 8bf719659406e4a1b56d441e0c7da2085d891d96, 529766e0a0114438887382a68d97341fbf8349fb < 82048795242f04275a3f49ffc66ad851b6120954, 5.2
Fixed: Linux: < 5.2, 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.

Evidence and provenance

Published 28 Aug 2026 · Last source change 29 Aug 2026, 06:22 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2

CVSS sourceCNA

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-28

European sourceENISA EUVD · EUVD-2026-67556

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceUnavailable

NVD statusNVD received

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

Material change intelligence

What changed after publication

View recent updates ↗

29 Aug 2026, 06:22 UTC
SeveritySeverity changed from Unknown to High.
Before
Unknown
After
High
CNA ↗
29 Aug 2026, 06:22 UTC
CVSS scoreCVSS score changed from not recorded to 7.8 (CVSS 3.1 · CNA · 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 · CNA · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
CNA ↗
28 Aug 2026, 14:12 UTC
ENISA EUVD mappingEUVD-2026-67556 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2026-67556"}
ENISA EUVD ↗
28 Aug 2026, 06:52 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2026-08-28CVE published

2026-08-29Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-67556↗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.

i2c: amd-mp2: Unregister callback on adapter add failure

Published severity in operational context

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

Release-specific package status

Authoritative vendor CSAF and VEX advisories

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

ENISA European Vulnerability Database

EUVD-2026-67556

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication