# CVE-2026-68374: usb: core: sysfs: add lock to bos_descriptors_read()

> A race condition in the Linux kernel USB core allows attackers to trigger a use-after-free, potentially leading to code execution or system 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:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-68374, DEBIAN-CVE-2026-68374, GHSA-hh3m-2ww4-7gxq, UBUNTU-CVE-2026-68374

## What is CVE-2026-68374?

CVE-2026-68374 is a high-severity use after free 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:

usb: core: sysfs: add lock to bos_descriptors_read()

Add a lock to the function bos_descriptors_read().

This function accesses udev->bos, which could be simultaneously freed in
usb_reset_and_verify_device(), a function that is commonly called in
drivers all over the kernel.

Weakness: CWE-416 (Use After Free)

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


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

Apply the vendor's patch.

## Is CVE-2026-68374 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68374 is a high-severity use after free 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-68374 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-68374/ (Markdown: https://insights.sbomify.com/CVE-2026-68374/index.md)
```

## Sources

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

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