** Description changed: [ Impact ] noble-stable-2026-06-16 introduced a patch with hunks that applied trivially despite using a field `eee_cfg` which is not in 6.8 context. Since the subsystem in which these mistakes were present is not compiled in generic by default, the compilation error was not caught until now. - In order to fix this issue, pick the changes which introduce `eee_cfg` - as a field of `struct phy_device`. + In order to fix this issue, revert the set of changes which introduce + `eee_cfg` in bcmasp. This will re-introduce CVE-2026-31506 which will be + remediated through a separate backport. [ Test Plan ] Kernel should compile properly after patch application. [ Where problems could occur ] - Since the previous state was already a regression, there is no real risk - of getting much worse. + This will re-introduce CVE-2026-31506 which will be remediated through a separate backport. Otherwise, the previous state was already a regression, + there is no real risk of getting much worse.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2158935 Title: Fix FTBFS on noble for kernels with bcmasp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158935/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
