Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

[Michael Biebl]

Am 20.02.2018 um 13:19 schrieb Gert Wollny:
> Am Dienstag, den 20.02.2018, 12:56 +0100 schrieb Michael Biebl:
>> Am 20.02.2018 um 12:40 schrieb Gert Wollny:
>>> However, while upstream is certainly correct that a kernel bug is
>>> the trigger of  the lockup, systemd should not hang on this,
>>> because if sending messages to systemd can lock up the system then
>>> this is actually an attack vector for a DoS attack. 
>>
>> How is this an attack vector for a DoS attack? Please elaborate
>>
> I don't really know by which channel systemd gets these messages that

timerfd

> make it lock up in this loop, but if someone can spoof this kind of
> message and the system locks up because of this, wouldn't this be a
> typical DoS attack?

How could an unprivileged user spoof such messages?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180220/50ca0977/attachment-0002.sig>