ipvs: filter some flags received in the backup server
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3a9f5459db60311643bfbadf019f6d5370f2f26a, Kernel 438a5335276614186d6a96b8e7bddce811ad4ad6, Kernel 45a93111835ccfea7d969ec73588e33745fd9834 and 5 more.
In the Linux kernel, the following vulnerability has been resolved: ipvs: filter some flags received in the backup server While the IPVS SYNC protocol is not secure by design we can still protect the backup server from messages that can wreak havoc. This commit addresses problems from received connection flags or their combinations. We now drop messages as follows: 1. the NO_CPORT+TEMPLATE combination allows lookups for normal connections to hit template which can break in many ways. While the master does not sync connections with NO_CPORT flag, i.e. before they are established, we still accept NO_CPORT without TEMPLATE. 2. ONE_PACKET: it is not sent by master, so we do not expect it in backup. Before now it was ignored by IP_VS_CONN_F_BACKUP_MASK for protocol v1 while protocol v0 created connections that are not hashed and dropped immediately. Better to apply the IP_VS_CONN_F_BACKUP_MASK also to the flags from v0 messages for consistency with v1.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.14, >=87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 <3a9f5459db60311643bfbadf019f6d5370f2f26a, >=87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 <438a5335276614186d6a96b8e7bddce811ad4ad6, >=87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 <45a93111835ccfea7d969ec73588e33745fd9834, >=87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 <55d033324f67a15ff56be6d38d6e87f644e0ed62, >=87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 <d7d33c9efa9d1a2f244a1a64ec9b540b0f8975a0, >=87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 <ef3cd6c0b826e50dc21653b32552e258de6fd51c, >=87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 <f4cd1db7d421e82945713a36084bb0c35b75b27e, >=87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 <f96e91748f6304668fe647e686d199d7207d36f1 | 3a9f5459db60311643bfbadf019f6d5370f2f26a, 438a5335276614186d6a96b8e7bddce811ad4ad6, 45a93111835ccfea7d969ec73588e33745fd9834, 55d033324f67a15ff56be6d38d6e87f644e0ed62, d7d33c9efa9d1a2f244a1a64ec9b540b0f8975a0, ef3cd6c0b826e50dc21653b32552e258de6fd51c, f4cd1db7d421e82945713a36084bb0c35b75b27e, f96e91748f6304668fe647e686d199d7207d36f1 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket