Control: tags -1 fixed-upstream - moreinfo On 2026-08-12 21:25:16 +0200, Salvatore Bonaccorso wrote: > The fix upstream would be: > > v7.0-rc1: 342ccffd9f77fc29fe1c05fd145e4d842bd2feaa drm/display/dp_mst: Add > protection against 0 vcpi
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=342ccffd9f77fc29fe1c05fd145e4d842bd2feaa which was committed on 2025-11-28, so the last time I got the issue (only a few days later), the kernel (6.*) did not have the fix. BTW, this is CVE-2025-71305: https://nvd.nist.gov/vuln/detail/CVE-2025-71305 > which got backported in turn as well to > > v6.1.165: 95dbd525efce2a9e9e1c50ad15213de644c85ad0 drm/display/dp_mst: Add > protection against 0 vcpi > v6.6.128: ac9a7c329a5610051fc476644c9b9145a5965ecb drm/display/dp_mst: Add > protection against 0 vcpi > v6.12.75: 3f44cdb5371faf225af37d5caba8f21ec0572469 drm/display/dp_mst: Add > protection against 0 vcpi > v6.18.16: 4d2ccdea18b564e3f73e3e543854acea64e6277d drm/display/dp_mst: Add > protection against 0 vcpi > > (but that is less relevant for this bug, if you are running unstable > kernel, so moving to the last kernel in unstable includes the above). Yes, the machine in question is running unstable (though I sometimes uses an older kernel due to another bug, which is not fixed yet). So I suppose that this bug could now be closed. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
