{mpellizzer, joseogando}
Speaking of verification, the issue only get appears after a significant
amount of uptime (i.e. the kernels started crashing months after the
initial deployment).
The BF3s that were crashing did not immediately crash after power
cycling despite the same traffic flows that could generate the same TC
filters.
Reproducing it has a significant timing aspect involved and we cannot
just trigger it at a random point in time.
So, w.r.t. the above bot message, in all honesty, I cannot verify it in
5 working days because there isn't a set of actions identified yet to
trigger a 100% reproducer.
The best I can do is run scenarios with the built kernel 5.15.0-1069.71
on one of the machines I have access to which involve creating a lot tc
filters and just make sure nothing breaks in normal conditions.
And once there is a singed build that can be rolled out onto SecureBoot-
enabled systems, I can roll it out on a large estate.
Would that work for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2109993
Title:
linux-bluefield is vulnerable to CVE-2025-21857
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2109993/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
