ppp: fix race conditions in ppp_fill_forward_path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f6efc675c9dd8d93f826b79ae7e33e03301db609 · < 0417adf367a0af11adf7ace849af4638cfb573f7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ppp: fix race conditions in ppp_fill_forward_path
ppp_fill_forward_path() has two race conditions:
1. The ppp->channels list can change between list_empty() and list_first_entry(), as ppp_lock() is not held. If the only channel is deleted in ppp_disconnect_channel(), list_first_entry() may access an empty head or a freed entry, and trigger a panic.
2. pch->chan can be NULL. When ppp_unregister_channel() is called, pch->chan is set to NULL before pch is removed from ppp->channels.
Fix these by using a lockless RCU approach: - Use list_first_or_null_rcu() to safely test and access the first list entry. - Convert list modifications on ppp->channels to their RCU variants and add synchronize_net() after removal. - Check for a NULL pch->chan before dereferencing it.
From the CVE record · Linux
The Linux kernel’s ppp_fill_forward_path() has race conditions involving changes to the PPP channel list and a channel pointer that can become NULL. Concurrent channel removal can cause a kernel panic; the input does not specify whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with PPP support should check their versions; affected versions are not specified.