11 comments

  • dayofthedaleks 1 hour ago
    The headline should include Trend Micro's name for shaming purposes. Amatuerish.
  • lynndotpy 56 minutes ago
    Still bleary eyed, but: Most severe ones are in SMB and KSMBD, which apparently have implementations in kernel space. I think this doesn't impact anyone not using KMB.

    Others are LPEs, but two have been deleted by now, so can't be sure of the details.

    TrendMicro's site opens up with a big big "Advancing AI-Native Security with Anthropic". Which checks out I guess.

  • wongarsu 56 minutes ago
    Doesn't the Linux kernel encourage reporting on the public mailing list for kernel vulnerabilities that were found using AI? If I remember correctly they introduced that policy after the security mailing list got swamped with multiple reports for the same vulnerabilities
    • smashed 20 minutes ago
      On first glance it seems you are right.

      > If you resorted to AI assistance to identify a bug, you must treat it as public. https://github.com/torvalds/linux/blob/master/Documentation/...

      • ReDress 3 minutes ago
        I don't think AI is of much concern, if you actually have a valid security issue.

        No-one, really will care if you discovered it via AI or otherwise. Because, the weight of the bug itself should outweight other concerns. This is how professional security works. There will always be one concern or the other about a bug but what carries more weight will determine the direction that the disclosure process takes.

        A valid security bug, by itself should carry enough technical weight that concerns about whether it was discovered through AI or otherwise should become irrelevant.

        Anyways, it mostly seems like people don't really care much about computer security at Linux. I would like to think they care more about infrastructure and related security issues because, well, if my computer is an open book, then why would security issues around it be a concern?

        Anyways...

        Enough said here - lol

  • ReDress 1 hour ago
    I'm not surprised because the disclosure process of https://hackerone.com is completely and openly public.

    But they have also disabled Linux as one of the products that they work with.

  • extraextra 1 hour ago
    What an entertaining season in the simulation
  • fguerraz 30 minutes ago
    Can we kick SMB implementations out of the kernel please? If not, can we please get PHP mainlined in the kernel?
    • ReDress 28 minutes ago
      SMB was "imported" into the kernel as an optimization for the user-space version - heh
  • ivanmontillam 1 hour ago
    It's being a great season, techsecurity-wise.
    • Avicebron 1 hour ago
      On HN everyone is a security engineer.
      • gilrain 1 hour ago
        They wanted "full stack", so they found hires with 1/10th of an education in each of 10 different fields.

        The boss class are rich because they're smart. /s

        • greenavocado 57 minutes ago
          > 1/10th of an education in each of 10 different fields combined FTFY
          • 0c3ca83 54 minutes ago
            But they're cheap 10x engineers.
  • jumperabg 39 minutes ago
    Finally the last vulnerabilities of the year.
    • cookiengineer 20 minutes ago
      > Finally the last vulnerabilities of the year ... until today

      Fixed that for you

  • NooneAtAll3 1 hour ago
    "accidentally"

    I feel paranoid enough now to blame ai companies to try to induce panic and proclaim "buy our product to save yourself"

    • pelagicAustral 1 hour ago
      Agree, wild stretch to accidentally send this loot to a mailing list.
    • ReDress 43 minutes ago
      To be honest and fair, in this situation I don't believe this is something accidental.

      It probably just happens that the security concerns at ZDI don't match the security concerns at Linux(the vendor).

      So, it turns out that this vendor is difficult to work with ....

      I mean - heh

  • ototot 1 hour ago
    are those posted by AI?
  • throwaway613746 9 minutes ago
    [dead]