ipvs: do not propagate one-packet flag to synced conns
Summary
| CVE | CVE-2026-80714 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-28 08:16:57 UTC |
| Updated | 2026-08-28 08:16:57 UTC |
| Description | 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 26ec037f9841e49cc5c615deb8e1e73e5beab2ca 06d1d9b56ef8132fbf85006885eb43d9510b8b02 git |
Not specified |
| CNA |
Linux |
Linux |
affected 26ec037f9841e49cc5c615deb8e1e73e5beab2ca acbdc276091b308ca7794acb86e761f8203e2f59 git |
Not specified |
| CNA |
Linux |
Linux |
affected 26ec037f9841e49cc5c615deb8e1e73e5beab2ca 300348e3ba1521b003d59825f97e24f9a6859688 git |
Not specified |
| CNA |
Linux |
Linux |
affected 26ec037f9841e49cc5c615deb8e1e73e5beab2ca 44af98cc7d5ef8e730488d5df1eecd5deeaa5947 git |
Not specified |
| CNA |
Linux |
Linux |
affected 26ec037f9841e49cc5c615deb8e1e73e5beab2ca 4649e6faeecdc2d44bfa6ccbe405eef27e55d816 git |
Not specified |
| CNA |
Linux |
Linux |
affected 26ec037f9841e49cc5c615deb8e1e73e5beab2ca b5ee5b266f833601ac4817f6df0bc496fc376a28 git |
Not specified |
| CNA |
Linux |
Linux |
affected 26ec037f9841e49cc5c615deb8e1e73e5beab2ca e7acfc990c29890c883d0d0ce3f737d003a43b44 git |
Not specified |
| CNA |
Linux |
Linux |
affected 26ec037f9841e49cc5c615deb8e1e73e5beab2ca a63d2dbaeb50a85d4c976b15a36e6b0c7113db5b git |
Not specified |
| CNA |
Linux |
Linux |
affected 2.6.36 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 2.6.36 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.10.265 5.10.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.216 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.183 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.151 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.103 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.44 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.8 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/06d1d9b56ef8132fbf85006885eb43d9510b8b02 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4649e6faeecdc2d44bfa6ccbe405eef27e55d816 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/b5ee5b266f833601ac4817f6df0bc496fc376a28 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/44af98cc7d5ef8e730488d5df1eecd5deeaa5947 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/300348e3ba1521b003d59825f97e24f9a6859688 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/e7acfc990c29890c883d0d0ce3f737d003a43b44 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/acbdc276091b308ca7794acb86e761f8203e2f59 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a63d2dbaeb50a85d4c976b15a36e6b0c7113db5b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.