# CVE-2026-68387: can: raw: add locking for raw flags bitfield

> A race condition in the Linux kernel CAN raw socket implementation allows concurrent access to flag bitfields, potentially leading to data corruption or system instability.

- **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-68387, DEBIAN-CVE-2026-68387, GHSA-4vh2-jr7c-6362, UBUNTU-CVE-2026-68387

## What is CVE-2026-68387?

CVE-2026-68387 is a high-severity 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:

can: raw: add locking for raw flags bitfield

With commit 890e5198a6e5 ("can: raw: use bitfields to store flags in
struct raw_sock") the formerly separate integer values have been integrated
into a single bitfield. This led to a read-modify-write operation when
changing a flag in raw_setsockopt() which now needs a locking to prevent
concurrent access.

Instead of adding a lock/unlock hell in each of the flag manipulations this
patch introduces a wrapper for a new raw_setsockopt_locked() function
analogue to the isotp_setsockopt[_locked]() approach in net/can/isotp.c

[mkl: use Closes tag instead of Link]

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


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

Apply the vendor's patch.

## Is CVE-2026-68387 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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