net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e2829ae5459ddb5fce526b2e84697edf6c0c3cef, Kernel 26b2bd70d22457556e2fa01cbf1192cb1a94d619, Kernel 37e3c878b183a115f9a114067f9ef3b408ad27fb and 12 more.
In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry In a case where skb with an unconfirmed ct entry gets cloned, we may end up committing both but with different sets of extensions. The series of events: 1. The first clone wants to commit and runs the helpers wiring up the extension pointer into the expectation list. 2. Then it looses the confirmation keeping the entry unconfirmed. 3. Second clone now wants to commit labels and adds the new extension for that breaking the pointer in the expectation list causing UAF on the destruction path later. While this is possible to trigger, there should be no practical network pipeline where committing both clones without modifications into the same zone is needed. So, let's just reset the entry in case for some reason we got an skb with a shared one during commit. This doesn't affect any known use cases, but avoids any potential problems with sharing and modification of the unconfirmed ct entry. The fixes tag points to the introduction of helpers, since that's the main UAF trigger for the sharing.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=cae3a2627520c3795b54533c5328b77af3405dbe <e2829ae5459ddb5fce526b2e84697edf6c0c3cef, >=cae3a2627520c3795b54533c5328b77af3405dbe <26b2bd70d22457556e2fa01cbf1192cb1a94d619, >=cae3a2627520c3795b54533c5328b77af3405dbe <37e3c878b183a115f9a114067f9ef3b408ad27fb, >=cae3a2627520c3795b54533c5328b77af3405dbe <457e0df1b5711fbeb7ba1b6bfd826f5ef30e7e55, >=cae3a2627520c3795b54533c5328b77af3405dbe <55e5256adf3940e71802e2f749cacf81518726b0, >=cae3a2627520c3795b54533c5328b77af3405dbe <707c2dc77891a874f4e8c52c285a511079164ec8, >=cae3a2627520c3795b54533c5328b77af3405dbe <de41ee24f77b0fc45397db3e277cae2adbd43dfe, >=cae3a2627520c3795b54533c5328b77af3405dbe <e0fa5ea434b7e8467ef3adc64e3858b1ca2a642d, =4.3 | e2829ae5459ddb5fce526b2e84697edf6c0c3cef, 26b2bd70d22457556e2fa01cbf1192cb1a94d619, 37e3c878b183a115f9a114067f9ef3b408ad27fb, 457e0df1b5711fbeb7ba1b6bfd826f5ef30e7e55, 55e5256adf3940e71802e2f749cacf81518726b0, 707c2dc77891a874f4e8c52c285a511079164ec8, de41ee24f77b0fc45397db3e277cae2adbd43dfe, e0fa5ea434b7e8467ef3adc64e3858b1ca2a642d |
| linux-kernel: Kernel | >=5.11.0 <5.15.222, >=5.16.0 <6.1.189, >=6.13.0 <6.18.55, >=6.19.0 <7.2.9, >=6.2.0 <6.6.158, >=6.7.0 <6.12.112, >=4.3.0 <5.10.271 | 5.15.222, 6.1.189, 6.18.55, 7.2.9, 6.6.158, 6.12.112, 5.10.271 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket