xfrm: Wait for RCU readers during policy netns exit
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.136, 6.12.83, 6.18.24, 6.19.14
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: xfrm: Wait for RCU readers during policy netns exit xfrm_policy_fini() frees the policy_bydst hash tables after flushing the policy work items and deleting all policies, but it does not wait for concurrent RCU readers to leave their read-side critical sections first. The policy_bydst tables are published via rcu_assign_pointer() and are looked up through rcu_dereference_check(), so netns teardown must also wait for an RCU grace period before freeing the table memory. Fix this by adding synchronize_rcu() before freeing the policy hash tables.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From e1e551bc56302b80ff930c966f9985095fb1b70d · fixed in b66920a3348c0f63ba18365248fa21fbf0b3a937; From e1e551bc56302b80ff930c966f9985095fb1b70d · fixed in 438b1f668ad58f46ce699bb48e4698a7839e3f9e; From e1e551bc56302b80ff930c966f9985095fb1b70d · fixed in 3733fce2871c9bca9dd18a1a23b1432ea215a094; From e1e551bc56302b80ff930c966f9985095fb1b70d · fixed in 33a3149dd81a1e2f52b80ee1e0fc380b39f3d028; From e1e551bc56302b80ff930c966f9985095fb1b70d · fixed in 069daad4f2ae9c5c108131995529d5f02392c446
- Linux Linux
4.9
- KernelLinux
From 4.9.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