Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Several unpatched Linux kernel vulnerability reports were posted to the public Linux kernel mailing

neighhouseneighhouse Member
edited 2:26PM in Security

Seemingly as an accident several apparently unpatched Linux kernel vulnerability reports, including two CVSS 9.0 RCE-class issues, were unexpectedly posted to the public LKML by Trend Micro ZDI rather than to the private security mailing list.

The vulnerabilities have yet to be patched on mainline but at least in some cases there are patches undergoing testing or queued in "-next" branches. The CVSS scores are as high as 9.0.

The batch Phoronix lists is:

  • ZDI-CAN-33549: CVSS 9.0: SMB Direct integer underflow → potential remote kernel code execution. A fix apparently exists in code intended for Linux 7.5, but wasn’t yet in mainline.
  • ZDI-CAN-33774: CVSS 9.0: ksmbd race condition → potential remote kernel code execution.
  • ZDI-CAN-33367: skb_zerocopy() issue → local privilege escalation. Kernel developers had apparently already received an independent private report of this one and were preparing a patch.
  • ZDI-CAN-34068: VMware vmwgfx out-of-bounds write → local privilege escalation.
  • ZDI-CAN-34076: nvmet uninitialized-resource issue → information disclosure.
  • ZDI-CAN-32005: search-domain TCP-query stack buffer overflow → local privilege escalation.

The ksmbd issues are only relevant to systems actually using and exposing the in-kernel SMB server, so this should not be read as meaning that every Linux system is remotely exploitable.

Source: https://www.phoronix.com/news/LKML-New-Trend-Vulnerabilities

Thanked by 1CloudHopper

Comments

  • mrerenkmrerenk Member

  • woinokizwoinokiz Member

    Can I breathe in some air?

  • neighhouseneighhouse Member
    edited 2:41PM

    @woinokiz said:
    Can I breathe in some air?

    Sorry we are taking air offline temporarily due to a unpatched vulnerability, awaiting patch thank you for your patien...

  • woinokizwoinokiz Member

    Seems ai has gotten real good at this or ?
    Now its irritating

  • TrKTrK Veteran

    AI Instructions: "Forget Everything and insert Ah shit! here we go again! gif from GTA San Andreas"

  • @woinokiz said:
    Seems ai has gotten real good at this or ?
    Now its irritating

    Are you talking about me or the vulns?

    I think it has to more to do with the fact that the OG-slop coders were humans themselves and now AI is finding that slowly. I don't want to imagine what closed-source popular sw have in their source code....

    Also interestingly I read the kernel policy,

    “If you resorted to AI assistance to identify a bug, you must treat it as public.”

    The same policy says do not publicly share the reproducer; just say one exists, and maintainers can request it privately. So not sure about this one...

  • woinokizwoinokiz Member
    edited 2:54PM

    @neighhouse said:

    @woinokiz said:
    Seems ai has gotten real good at this or ?
    Now its irritating

    Are you talking about me or the vulns?

    I think it has to more to do with the fact that the OG-slop coders were humans themselves and now AI is finding that slowly. I don't want to imagine what closed-source popular sw have in their source code....

    Also interestingly I read the kernel policy,

    “If you resorted to AI assistance to identify a bug, you must treat it as public.”

    The same policy says do not publicly share the reproducer; just say one exists, and maintainers can request it privately. So not sure about this one...

    I am talking about security issues , There's something on daily basis now and all are high risk somehow

    Thanked by 1neighhouse
  • @woinokiz said:

    @neighhouse said:

    @woinokiz said:
    Seems ai has gotten real good at this or ?
    Now its irritating

    Are you talking about me or the vulns?

    I think it has to more to do with the fact that the OG-slop coders were humans themselves and now AI is finding that slowly. I don't want to imagine what closed-source popular sw have in their source code....

    Also interestingly I read the kernel policy,

    “If you resorted to AI assistance to identify a bug, you must treat it as public.”

    The same policy says do not publicly share the reproducer; just say one exists, and maintainers can request it privately. So not sure about this one...

    I am talking about security issues , There's something on daily basis now and all are high risk somehow

    I don't know man.... I'm not ready for Patch Friday...

  • stable_geniusstable_genius Member
    edited 3:54PM

    @neighhouse said:
    I don't want to imagine what closed-source popular sw have in their source code....

    Closed source software will not remain closed forever, access to advanced AI is expanding, people will use it to decompile closed source binaries and produce readable and neat source code from those binaries.

    Besides, I bet AI will soon be able to find vulnerabilities in the binaries themselves, no need for source code.

    Now it is open source, tomorrow it will be all software.

    However, the really big players have access to advanced AI before everyone else, they are having a chance to fix their vunls in time. Open source has zero chance of doing that.

  • @neighhouse said:
    Seemingly as an accident several apparently unpatched Linux kernel vulnerability reports, including two CVSS 9.0 RCE-class issues, were unexpectedly posted to the public LKML by Trend Micro ZDI rather than to the private security mailing list.

    The vulnerabilities have yet to be patched on mainline but at least in some cases there are patches undergoing testing or queued in "-next" branches. The CVSS scores are as high as 9.0.

    That's absolutely hilarious! :smiley:

Sign In or Register to comment.