> LLMs are always hallucinating that they've found the most severe bug in software history.

That is a function of the training data/method, like many of AI's problems. This doesn't stop it being a problem of course, but it shouldn't be a surprise.

Big bugs, like heartbleed, over the years have had breathy websites going over how serious the problem is because the problem was that serious, so the models associate that sort of wording with bug reports. Less serious bugs don't get the same excited treatment, repeated in many many places, so more measured descriptions figure in the training data relatively less.

Good point, I don't know! That's why I formulated it this way. Edit: I guess what I'm trying to say is, with security relevant things it might do no harm to be a bit more credulous when it comes to initial reports. (In theory, no idea how to best handle the growing flood of LLM generated stuff. Pointing LLMs at each other doesn't seem great.)

As far as I can tell the next ASB will fix this issue... maybe they simply forgot to tell you :/

EDIT: actually already fixed in https://review.lineageos.org/c/LineageOS/android_frameworks_...

There's yet another PDU fixup that stems from negative index

That's unfortunate. They need to do some kind of triage then, I hope this doesn't mean that they're constantly busy now with equally bad or worse bugs, but I guess it wouldn't be too surprising.

Ironic comment from someone who literally just submitted an AI slop report and went so far as to give it a website and cutsey name to attempt to feign legitimacy and skill behind the "researcher."