# CVE-2026-68314: net: mctp i3c: clean up notifier and buses if driver register fails

> A failure in MCTP I3C driver registration leaves dangling pointers and leaked memory, potentially causing system instability or crashes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68314, DEBIAN-CVE-2026-68314, GHSA-432r-7fw5-c4hj, UBUNTU-CVE-2026-68314

## What is CVE-2026-68314?

CVE-2026-68314 is a high-severity memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

net: mctp i3c: clean up notifier and buses if driver register fails

mctp_i3c_mod_init() registers the I3C bus notifier and then walks the
existing buses with i3c_for_each_bus_locked(mctp_i3c_bus_add_new, NULL)
before registering the I3C device driver.  If i3c_driver_register()
fails, the function returns the error directly, leaving the notifier
registered and every mctp_i3c_bus object created for the existing buses
allocated.  The notifier is left pointing into the module that failed to
load and the bus list is leaked.

Mirror the module exit path on this failure: unregister the notifier and
tear down the buses that were added before returning the error.

This issue was identified during our ongoing static-analysis research while
reviewing kernel code.

## Which versions are affected by CVE-2026-68314?


## How do I fix CVE-2026-68314?

Apply the vendor's patch.

## Is CVE-2026-68314 being exploited?

There is no known exploitation of CVE-2026-68314 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68314 and fix it if it is affected.

What it is: CVE-2026-68314 is a high-severity memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68314 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68314/ (Markdown: https://insights.sbomify.com/CVE-2026-68314/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68314
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68314
- OSV: https://osv.dev/vulnerability/CVE-2026-68314

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68314/
Summaries are generated and may contain mistakes; the official description above is the record.