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.
- 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
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.
Sources
Also known as BELL-CVE-2026-68387, DEBIAN-CVE-2026-68387, GHSA-4vh2-jr7c-6362, UBUNTU-CVE-2026-68387.