can: bcm: add missing rcu read protection for procfs content
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f1b4e32aca0811aa011c76e5d6cf2fa19224b386 · < 63567ecd99a24495208dc860d50fb17440043006| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
can: bcm: add missing rcu read protection for procfs content
When the procfs content is generated for a bcm_op which is in the process to be removed the procfs output might show unreliable data (UAF).
As the removal of bcm_op's is already implemented with rcu handling this patch adds the missing rcu_read_lock() and makes sure the list entries are properly removed under rcu protection.
From the CVE record · Linux
The Linux kernel lacks RCU read protection when generating CAN BCM procfs content. If a bcm_op is removed while that content is generated, the output may show unreliable data due to a use-after-free. The input does not specify access requirements or whether user interaction is needed.
Operators running the Linux kernel should check their versions against the vendor advisory; affected versions were not provided.