The Linux kernel's CAN raw socket driver suffered from a race condition caused by adding a bitfield for flag storage without proper locking. Concurrent calls to raw_setsockopt() performed read-modify-write operations on the shared bitfield, allowing two threads to interleave in a way that could lose updates or corrupt kernel memory. This flaw could lead to kernel data corruption, service disruption, or potentially privilege escalation if exploited. The weakness is a classic concurrency issue and is aligned with the CWE-362 "Race Condition" vulnerability class.

All Linux kernel releases prior to the commit that introduced locking for the raw CAN socket flag bitfield are affected. The vulnerability is specific to the plain CAN driver (can: raw). As the commit referenced by the CVE integrates sub‑components of the kernel, the issue spans the Linux kernel as a whole rather than a single module, so any system running an unpatched kernel version is potentially impacted.

No EPSS score is available, indicating that public exploitation data is not currently in the database, and the vulnerability is not listed in CISA's KEV catalog. Nonetheless, the lack of synchronization creates a medium‑to‑high risk scenario. An attacker with the ability to open multiple raw CAN sockets (for example, running as a privileged user or exploiting local privilege escalation) could trigger the race condition, causing corruption or denial of service. Because the flaw resides in kernel code, its exploitation requires local or specialized access; it is unlikely to be remotely exploitable without additional vectors.