Matthias Reineke (Customer) asked a question.

Is Kemp LoadMaster affected by CVE-2026-98432?

Hi,

 

could you please confirm whether Kemp LoadMaster (LMOS) is affected by the recently disclosed Linux kernel vulnerability CVE-2026-98432?

 

In particular, is the vulnerability remotely exploitable through publicly accessible Virtual Services, including Layer 7 services with transparency enabled?

 

If affected, are any mitigations available, and when can we expect a security update?

 

Thanks in advance!


  • Andrew Spagnuolo (Progress Software)

    Hello all,

     

    Just following up. Development is still investigating, however speaking with them this morning, since MPTCP is not enabled on the loadmaster LMOS Kernel (The publicly discussed remote-root exploit path for this CVE was MPTCP-specific), they do not believe the loadmaster is vulnerable to this CVE. They do want to of course do their due diligence and get 100% clarification for this before making any announcements.

     

    We will be sending out an official announcement once they have fully conducted their analysis.

     

    We appreciate all of your patience on this as we continue working through it.

     

    I also want to make it clear that because this is selected as "Best Answer" does not mean this forum is closed. We still encourage further discussion below. This pinned comment will be used as a way to provide the latest updates on the status of this CVE and its relation to the LoadMaster appliance.

     

    Update 11/17

     

    Hello all,

     

    We appreciate your patience with this as we worked through not only identifying the LoadMasters vulnerability status, but also developing a hotfix for it.

     

    We have addressed the issues and have developed and tested a patch that is now available.

     

    Currently, we have not received any reports that this vulnerability has been exploited, and we are not aware of any direct operational impact on customers.

     

    The hotfix which resolves this CVE is firmware versions GA 7.2.63.4. and LTS 7.2.54.20

     

    Below are the links for the firmware downloads:

     

    https://community.progress.com/s/article/LoadMaster-Critical-Security-Vulnerability-CVE-2026-98432

     

    If you have any questions, please let us know below or open a support ticket with us directly for more immediate assistance. https://community.progress.com/s/supportlink-landing

     

    Thank you,

    Selected as Best
  • Nichol Goldstein (Progress)

    Hi all,

    The Progress team is out for the weekend, but I escalated this to try and get you an answer ASAP. (Please note that my LoadMaster moderator works during American business hours.)

  • Andrew Spagnuolo (Progress Software)

    Our developers are aware of this CVE and are working to confirm if the loadmaster is vulnerable or not. We will update you as soon as we have this information. I would expect an answer within the next day or two. We appreciate your patience with this.

    • Allen Steckling (Customer)

      If kemp is vulnerable to this CVE they will all be compromised within hours. If they haven't been already. "A day or two" is far too long.

  • Darren DeHaven (CREDENCE)

    * KEMP Linux kernel version:  4.14.137 per

    https://community.progress.com/s/article/What-Version-of-Linux-Does-the-LoadMaster-use

     

    * Below is a response from an AI chat, when I asked if linux kernel 4.14.137 is affected or not:

    Most likely yes, kernel 4.14.137 falls inside the affected range for CVE-2026-98432.

    Why 4.14.137 is in range: CVE-2026-98432 (CVSS 9.8, critical) is a use-after-free vulnerability in the Linux kernel's IPv4 TCP (Transmission Control Protocol) handshake path, affecting kernels dating back to version 4.4. The kernel CVE team's announcement says the bug was introduced in Linux 4.4, and 4.14 is later than 4.4. The core flaw is a race condition when processing SYN packets containing IPv4 options. A SYN packet is the first packet of a TCP connection. The fix landed in the mainline kernel on 2026-09-17.

    No upstream fix exists for 4.14. Without looking it up: the upstream 4.14 long-term-support branch reached end of life in early 2024, and 4.14.137 itself dates from around August 2019. A vanilla 4.14.137 kernel will therefore never get an upstream patch for CVE-2026-98432. The fix is to move to a supported kernel.

    One partial difference for 4.14: The publicly demonstrated exploit uses a specific path. Anthropic's exploit specifically concerns multipath TCP (MPTCP), which is not used by every service. Upstream MPTCP was not merged until kernel 5.6, so a stock 4.14 kernel lacks that path. The underlying IPv4-options use-after-free bug is still present, though. Treat the 4.14.137 host as vulnerable.

    Vendor kernels can differ. If "4.14.137" is a distribution's version string, the vendor's advisory decides the answer, because vendors backport fixes. Amazon Linux 2 is a common example of a distribution that ships 4.14-based kernels. One tracker lists Amazon Linux as patched and points to AWS security bulletin 2026-160-AWS. Check that bulletin, or run

    rpm -q --changelog kernel | grep CVE-2026-98432

    on Amazon Linux or RHEL-family hosts.

    Interim mitigation for an unpatchable 4.14 host: Red Hat published an nftables (the Linux packet-filtering framework) rule that drops TCP packets carrying IPv4 options. It is a partial mitigation, but a sane defense as long as you expect it won't break your services:

    table inet cve_2026_98432 {

    chain input {

    type filter hook input priority -310; policy accept;

    ip protocol tcp ip hdrlength > 5 counter drop

    }

    }

    The rule matches packets whose IPv4 header length (IHL) is greater than 5 words (20 bytes), which means the header contains options. Legitimate traffic with IPv4 options is rare. On a 4.14 host without nftables, the iptables equivalent is a rule on the INPUT chain in the

    raw

     

    table that drops TCP packets with an IHL greater than 5, using the

    u32

    match. Upgrading the kernel is still the real fix.

  • Matthias Reineke (Customer)

    AWS has confirmed that CVE-2026-98432 affects Linux kernel versions 4.4 and later, including the 4.14 series used by Amazon Linux 2, and has released a security fix.

     

    Since Kemp LoadMaster reportedly uses Linux kernel 4.14.137, this raises concerns about potential exposure unless Kemp has already applied the relevant fix.

     

    Official AWS Security Bulletin:

    https://aws.amazon.com/security/security-bulletins/2026-160-aws/

     

  • Matthias Reineke (Customer)

    CVE-2026-98432 – Timeline

     

    • October 5, 2026: The Linux kernel fix was committed. The vulnerability was known to the involved kernel developers by this date.
    • October 15, 2026: CVE-2026-98432 was publicly disclosed.
    • October 30, 2026: AWS and Red Hat published security advisories addressing the vulnerability.
    • November 2, 2026: Progress/Kemp confirmed that its developers are aware of the CVE but are still investigating whether LoadMaster is affected.

     

    18 days after public disclosure, there is still no confirmed vulnerability assessment or published mitigation guidance for Kemp LoadMaster.

     

     

  • Clark Kent (Customer)

    OK, Kemp LoadMaster is affected by CVE-2026-98432 !!! Are any mitigations available, and when can we expect a security update?

    • Matthias Reineke (Customer)

      Did you get a corresponding answer from Progress/Kemp? Where does the information come from?

10 of 26