Vulnerability 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]
CVSS Score
HIGH
References
- https://git.kernel.org/stable/c/00ba4bf8798242253fefc1fa6a78db1d445fd024
- https://git.kernel.org/stable/c/1e5185c090589f4146d728ab36417d8a5419f127
- https://git.kernel.org/stable/c/57791aab1129c9405f84bb0882de58967d8b44cd
FAQ
What is CVE-2026-68387?
CVE-2026-68387 is a vulnerability with a CVSS score of 7.8 (HIGH). 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"...
How severe is CVE-2026-68387?
CVE-2026-68387 has been rated HIGH with a CVSS base score of 7.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-68387?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.