# CVE-2026-74629: net/dibs: Correct freeing of dmb_clientid_arr

> A use-after-free and double-free vulnerability in the Linux kernel's dibs driver allows attackers to potentially execute code or cause a system crash.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-74629, DEBIAN-CVE-2026-74629, GHSA-8jrf-fhpg-2ggp, UBUNTU-CVE-2026-74629

## What is CVE-2026-74629?

CVE-2026-74629 is a high-severity use after free vulnerability in Linux, published on 22 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/dibs: Correct freeing of dmb_clientid_arr

A dibs device interrupt handler can be active after dibs_dev_del() and
may still access dmb_clientid_arr. (UAF)

In case of a failure in dibs_dev_add() being called by dibs_lo_dev_probe()
dmb_clientid_arr is freed twice (double free).

Free dmb_clientid_arr in dibs_dev_release() after last reference is gone.
Note that allocating in dibs_dev_add() instead of dibs_dev_alloc() is ok
for now, because no dmbs can be registered before dibs_dev_add().

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


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

Apply the vendor's patch.

## Is CVE-2026-74629 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74629 is a high-severity use after free vulnerability in Linux, published on 22 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-74629 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-74629/ (Markdown: https://insights.sbomify.com/CVE-2026-74629/index.md)
```

## Sources

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

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