FWIW I'm fairly convinced that the first vulnerable version for CVE-2020-5310
is 6.0.0, which is the first release that included
https://github.com/python-pillow/Pillow/commit/e91b851fdc1c914419543f485bdbaa010790719f
which introduced
the overflow when switching away from the safer TIFFTileSize
> Alternatively, it could be related to:
> https://www.sqlite.org/src/info/4feb3159c6bc3f7e33959
>
> This was released as a part of 3.27.2 and looks like it has the right
> text as well. What concerns me is that the ticket[0] is almost a week
> before TALOS's timeline for "Vendor patched" plus it
On Saturday 11 September 2010, you wrote:
> On 09/11/2010 06:24 PM, Robert Scott wrote:
> > Blacklisting the 855GM from KMS in 2.6.32-21 to fix bugs like 582105
> > seems to be causing my system to hard lock when X starts up. Magic
> > sysrq key does nothing, and of course th
Package: linux-image-2.6.32-5-686
Version: 2.6.32-21
Severity: grave
Hi,
Blacklisting the 855GM from KMS in 2.6.32-21 to fix bugs like 582105 seems to
be causing my system to hard lock when X starts up. Magic sysrq key does
nothing, and of course the 855GM being totally blacklisted means modese
4 matches
Mail list logo
