Comment by alentred
15 days ago
To be fair: while critical (9.8) it has an EPSS score of <1% (probability of it being actually used). According to [1], [2], and others, at worst the issue results in a kernel crash or a denial of service. I read the post by Anthropic too, but something just doesn't reconcile there between everyone saying its a DoS, and Anthropic alone claiming RCE. So far the advisories I read state "under specific conditions ... result in a kernel crash" and similar.
[1] https://app.opencve.io/cve/CVE-2026-98432 [2] https://aws.amazon.com/security/security-bulletins/2026-160-...
As the days pass the probability of it being actually used is increasing. The EPSS score is clearly just an estimate, and according to the nist cve database, attack complexity is low so I would take the EPSS score with a grain of salt.
I had the same question about the actual exploit on another thread: https://news.ycombinator.com/item?id=50319143
It’s only recently I realised that a lot of these very clever vulnerabilities are often not actually exploitable, except in quite specific conditions.
Something like this is rowhammer. Can it be exploited in a lab setting vs practically in the wild? Is fail2ban + WAF sufficient? How much network traffic is needed to remotely trigger the exploit in the field? How much inside knowledge of the system itself needs to be known?
These go from extreme edge cases to viable approaches over time, so it needs to be patched. I think the really messed up thing is the lack of communication from the Ubuntu team. If they have a rationale either way, that's fine. They may disagree on the severity, identified a problem in the fix, etc, but the lack of transparency is causing a loss of confidence in the team's abilities.