Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. Apparently there's yet another #LinuxKernel Local Privilege Escalation #vulnerability.

Apparently there's yet another #LinuxKernel Local Privilege Escalation #vulnerability.

Scheduled Pinned Locked Moved Uncategorized
linuxkernelvulnerabilityinfoseccybersecuritycve202643284
7 Posts 4 Posters 18 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • harrysintonen@infosec.exchangeH This user is from outside of this forum
    harrysintonen@infosec.exchangeH This user is from outside of this forum
    harrysintonen@infosec.exchange
    wrote last edited by
    #1

    Apparently there's yet another #LinuxKernel Local Privilege Escalation #vulnerability. There's a mitigation that disables esp4, esp6 and rxrpc modules.

    Link Preview Image
    oss-security - Dirty Frag: Universal Linux LPE

    favicon

    (www.openwall.com)

    Link Preview Image
    GitHub - V4bel/dirtyfrag

    Contribute to V4bel/dirtyfrag development by creating an account on GitHub.

    favicon

    GitHub (github.com)

    EDIT: The related vulnerabilities are now tracked as CVE-2026-43284 and CVE-2026-43500. https://nvd.nist.gov/vuln/detail/CVE-2026-43284 https://nvd.nist.gov/vuln/detail/CVE-2026-43500

    #infosec #cybersecurity #CVE_2026_43284 #CVE_2026_43500

    gtsadmin@wiseowl.clubG harrysintonen@infosec.exchangeH labanskoller@infosec.exchangeL 3 Replies Last reply
    0
    • harrysintonen@infosec.exchangeH harrysintonen@infosec.exchange

      Apparently there's yet another #LinuxKernel Local Privilege Escalation #vulnerability. There's a mitigation that disables esp4, esp6 and rxrpc modules.

      Link Preview Image
      oss-security - Dirty Frag: Universal Linux LPE

      favicon

      (www.openwall.com)

      Link Preview Image
      GitHub - V4bel/dirtyfrag

      Contribute to V4bel/dirtyfrag development by creating an account on GitHub.

      favicon

      GitHub (github.com)

      EDIT: The related vulnerabilities are now tracked as CVE-2026-43284 and CVE-2026-43500. https://nvd.nist.gov/vuln/detail/CVE-2026-43284 https://nvd.nist.gov/vuln/detail/CVE-2026-43500

      #infosec #cybersecurity #CVE_2026_43284 #CVE_2026_43500

      gtsadmin@wiseowl.clubG This user is from outside of this forum
      gtsadmin@wiseowl.clubG This user is from outside of this forum
      gtsadmin@wiseowl.club
      wrote last edited by
      #2

      @harrysintonen None of my #Debian #linux boxen have those kernel modules loaded:
      sudo lsmod | egrep "esp4|esp6|rxrpc"
      #InfoSec

      harrysintonen@infosec.exchangeH 1 Reply Last reply
      0
      • gtsadmin@wiseowl.clubG gtsadmin@wiseowl.club

        @harrysintonen None of my #Debian #linux boxen have those kernel modules loaded:
        sudo lsmod | egrep "esp4|esp6|rxrpc"
        #InfoSec

        harrysintonen@infosec.exchangeH This user is from outside of this forum
        harrysintonen@infosec.exchangeH This user is from outside of this forum
        harrysintonen@infosec.exchange
        wrote last edited by
        #3

        @gtsadmin They will be loaded by the kernel automatically on demand. So apply the mitigation until kernel update is available.

        1 Reply Last reply
        0
        • harrysintonen@infosec.exchangeH harrysintonen@infosec.exchange

          Apparently there's yet another #LinuxKernel Local Privilege Escalation #vulnerability. There's a mitigation that disables esp4, esp6 and rxrpc modules.

          Link Preview Image
          oss-security - Dirty Frag: Universal Linux LPE

          favicon

          (www.openwall.com)

          Link Preview Image
          GitHub - V4bel/dirtyfrag

          Contribute to V4bel/dirtyfrag development by creating an account on GitHub.

          favicon

          GitHub (github.com)

          EDIT: The related vulnerabilities are now tracked as CVE-2026-43284 and CVE-2026-43500. https://nvd.nist.gov/vuln/detail/CVE-2026-43284 https://nvd.nist.gov/vuln/detail/CVE-2026-43500

          #infosec #cybersecurity #CVE_2026_43284 #CVE_2026_43500

          harrysintonen@infosec.exchangeH This user is from outside of this forum
          harrysintonen@infosec.exchangeH This user is from outside of this forum
          harrysintonen@infosec.exchange
          wrote last edited by
          #4

          Note that if you tested the exploit locally and then applied the workaround your system will retain the tampered kernel cache and will remain vulnerable even when the module is no longer in memory and cannot no longer be loaded.

          You can use sudo sh -c "echo 3 > /proc/sys/vm/drop_caches" to flush the exploit from memory. Rebooting will also work, of course.

          EDIT: Needless to say you should not execute random exploits in any important system. Always use a dedicated VM you can wipe after testing.

          christopherkunz@chaos.socialC 1 Reply Last reply
          0
          • harrysintonen@infosec.exchangeH harrysintonen@infosec.exchange

            Note that if you tested the exploit locally and then applied the workaround your system will retain the tampered kernel cache and will remain vulnerable even when the module is no longer in memory and cannot no longer be loaded.

            You can use sudo sh -c "echo 3 > /proc/sys/vm/drop_caches" to flush the exploit from memory. Rebooting will also work, of course.

            EDIT: Needless to say you should not execute random exploits in any important system. Always use a dedicated VM you can wipe after testing.

            christopherkunz@chaos.socialC This user is from outside of this forum
            christopherkunz@chaos.socialC This user is from outside of this forum
            christopherkunz@chaos.social
            wrote last edited by
            #5

            @harrysintonen In addition to Dirtyfrag, there there's Copy Fail 2 - Electric Boogaloo. https://github.com/0xdeadbeefnetwork/Copy_Fail2-Electric_Boogaloo This sets up an ESP interface and exploits a bug in the ESP-in-UDP code.
            Same here, probably prudent to drop caches (restart networking?) and remove the uid0 entry from /etc/passwd

            harrysintonen@infosec.exchangeH 1 Reply Last reply
            0
            • christopherkunz@chaos.socialC christopherkunz@chaos.social

              @harrysintonen In addition to Dirtyfrag, there there's Copy Fail 2 - Electric Boogaloo. https://github.com/0xdeadbeefnetwork/Copy_Fail2-Electric_Boogaloo This sets up an ESP interface and exploits a bug in the ESP-in-UDP code.
              Same here, probably prudent to drop caches (restart networking?) and remove the uid0 entry from /etc/passwd

              harrysintonen@infosec.exchangeH This user is from outside of this forum
              harrysintonen@infosec.exchangeH This user is from outside of this forum
              harrysintonen@infosec.exchange
              wrote last edited by
              #6

              @christopherkunz Sure if you executed that particular exploit you definitely must restore the /etc/passwd afterwards.

              1 Reply Last reply
              0
              • harrysintonen@infosec.exchangeH harrysintonen@infosec.exchange

                Apparently there's yet another #LinuxKernel Local Privilege Escalation #vulnerability. There's a mitigation that disables esp4, esp6 and rxrpc modules.

                Link Preview Image
                oss-security - Dirty Frag: Universal Linux LPE

                favicon

                (www.openwall.com)

                Link Preview Image
                GitHub - V4bel/dirtyfrag

                Contribute to V4bel/dirtyfrag development by creating an account on GitHub.

                favicon

                GitHub (github.com)

                EDIT: The related vulnerabilities are now tracked as CVE-2026-43284 and CVE-2026-43500. https://nvd.nist.gov/vuln/detail/CVE-2026-43284 https://nvd.nist.gov/vuln/detail/CVE-2026-43500

                #infosec #cybersecurity #CVE_2026_43284 #CVE_2026_43500

                labanskoller@infosec.exchangeL This user is from outside of this forum
                labanskoller@infosec.exchangeL This user is from outside of this forum
                labanskoller@infosec.exchange
                wrote last edited by
                #7

                @harrysintonen yesterday I read that one should not drop caches in a production system. I don’t know if that recommendation was just for performance or if all hell could break loose.

                1 Reply Last reply
                1
                0
                • R relay@relay.infosec.exchange shared this topic
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • World
                • Users
                • Groups