ipvs: do not propagate one-packet flag to synced conns
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 26ec037f9841e49cc5c615deb8e1e73e5beab2ca · < b5ee5b266f833601ac4817f6df0bc496fc376a28| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipvs: do not propagate one-packet flag to synced conns
Synced connections can be created before their destination exists. When the destination is later added, ip_vs_bind_dest() copies connection flags from the destination into cp->flags.
IP_VS_CONN_F_ONE_PACKET connections are not synced. If a synced connection inherits IP_VS_CONN_F_ONE_PACKET while it is already hashed, expiry can treat it as a one-packet connection and skip unlinking the existing conn_tab node, leaving stale hash nodes pointing at a freed struct ip_vs_conn.
Drop IP_VS_CONN_F_ONE_PACKET from destination flags when binding synced connections.
From the CVE record · Linux
In the Linux kernel’s IPVS code, a synced connection created before its destination exists can inherit a one-packet flag when the destination is added. On expiry, this can leave a stale hash node pointing to a freed connection. The input does not specify attacker access requirements or whether user interaction is needed.
Operators running Linux kernels with IPVS connection synchronization should check their versions; affected versions were not provided.