public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Allen Pais <apais@linux.microsoft.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Regression Impact from Commit dceb683ab87c on Kubernetes Hairpin Tests
Date: Wed, 12 Jun 2024 10:57:03 -0700	[thread overview]
Message-ID: <AD9EB3AD-7A36-4E54-9BEC-02584A4DF11E@linux.microsoft.com> (raw)

Hi Greg,

I hope this message finds you well. I'm reaching out to report a regression issue linked
to the commit dceb683ab87c(v5.15.158), which addresses the netfilter subsystem by skipping
the conntrack input hook for promiscuous packets. 

[dceb683ab87c 2024-04-09 netfilter: br_netfilter: skip conntrack input hook for promiscuous packets.]

Unfortunately, this update appears to be breaking Kubernetes hairpin tests, impacting the normal
functionality expected in Kubernetes environments.

Additionally, it's worth noting that this specific commit is associated with a security vulnerability,
as detailed in the NVD: CVE-2024-27018. 

We have bisected the issue to the specific commit dceb683ab87c. By reverting this commit,
we confirmed that the Kubernetes hairpin test issues are resolved. However, given that this commit 
addresses the security vulnerability CVE-2024-27018, directly reverting it is not a viable option. We’re 
in a tricky position and would greatly appreciate your advice on how we might approach this problem.

Thank you for your attention to this matter. I look forward to your guidance on how we might proceed.


Best regards,

Allen

             reply	other threads:[~2024-06-12 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 17:57 Allen Pais [this message]
2024-06-12 18:49 ` Regression Impact from Commit dceb683ab87c on Kubernetes Hairpin Tests Greg KH
2024-06-13 17:56   ` Allen Pais

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AD9EB3AD-7A36-4E54-9BEC-02584A4DF11E@linux.microsoft.com \
    --to=apais@linux.microsoft.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox