net: add proper RCU protection to /proc/net/ptype
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: add proper RCU protection to /proc/net/ptype
Yin Fengwei reported an RCU stall in ptype_seq_show() and provided a patch.
Real issue is that ptype_seq_next() and ptype_seq_show() violate RCU rules.
ptype_seq_show() runs under rcu_read_lock(), and reads pt->dev to get device name without any barrier.
At the same time, concurrent writers can remove a packet_type structure (which is correctly freed after an RCU grace period) and clear pt->dev without an RCU grace period.
Define ptype_iter_state to carry a dev pointer along seq_net_private:
struct ptype_iter_state { struct seq_net_private p; struct net_device *dev; // added in this patch };
From the CVE record · Linux
The Linux kernel's /proc/net/ptype handling lacks proper RCU protection when reading packet-type device pointers and advancing through the list. Reading this proc entry while packet-type structures are changed concurrently can cause an RCU stall. The input does not specify authentication requirements or an attacker-controlled trigger.
Engineers running Linux kernels should check their versions; the affected version range was not provided.