| 2023-03-27 14:41:34 |
Naveen chand |
bug |
|
|
added bug |
| 2023-03-27 14:56:14 |
Nick Rosbrook |
nominated for series |
|
Ubuntu Focal |
|
| 2023-03-27 14:56:14 |
Nick Rosbrook |
bug task added |
|
systemd (Ubuntu Focal) |
|
| 2023-03-27 14:56:22 |
Nick Rosbrook |
systemd (Ubuntu): status |
New |
Fix Released |
|
| 2023-03-27 14:56:36 |
Nick Rosbrook |
systemd (Ubuntu Focal): status |
New |
Triaged |
|
| 2023-03-27 18:13:47 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/439761 |
|
| 2023-04-06 14:17:59 |
Nick Rosbrook |
description |
[ Impact ]
The continuous systemd-resolved crashes delay/hang the device startup.
And this leads to unresponsive devices in the system.
[ Test Plan ]
The exact steps to reproduce this issue are still not known.
But we see this crash only in Static IP Addressing mode enabled, where systemd-resolved is enabled for LLMNR service.
But we were not able to see this crash in DHCP mode.
Steps to reproduce:
1) Powercycle the device.
2) Soft-reboot.
[ Where problems could occur ]
https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b.
This commit is resolving the issue which is observed.
Please refer to the above commit to assess the risk involved. |
[ Impact ]
The continuous systemd-resolved crashes delay/hang the device startup.
And this leads to unresponsive devices in the system. Specifically, the crash looks like:
Dec 16 12:51:21 TREND-24-AF-7A systemd[1]: Started Time & Date Service.
Dec 16 12:51:24 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=11/SEGV
[...]
Dec 16 12:53:47 TREND-24-AF-7A systemd-resolved[2591]: Assertion 'DNS_TRANSACTION_IS_LIVE(q->state)' failed at src/resolve/resolved-dns-query.c:520, function dns_query_complete(). Aborting.
Dec 16 12:53:47 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=6/ABRT
[ Test Plan ]
The exact steps to reproduce this issue are still not known.
But we see this crash only in Static IP Addressing mode enabled, where systemd-resolved is enabled for LLMNR service.
But we were not able to see this crash in DHCP mode.
Steps to reproduce:
1) Powercycle the device.
2) Soft-reboot.
[ Where problems could occur ]
The patch[1] simply disables the timer event source for a DNS query when the struct representing that query is free'd. I cannot see any realistic regression potential, because if the timer event fired on the DNS query after it has been free'd, then that would be this bug. I.e. no working code should be relying on the timer event source still being around after the query is free'd.
[1] https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b |
|
| 2023-04-06 14:39:08 |
Nick Rosbrook |
summary |
Systemd-resolved is crashing |
systemd-resolved crashes due to use-after-free bug |
|
| 2023-05-22 20:34:12 |
Nick Rosbrook |
description |
[ Impact ]
The continuous systemd-resolved crashes delay/hang the device startup.
And this leads to unresponsive devices in the system. Specifically, the crash looks like:
Dec 16 12:51:21 TREND-24-AF-7A systemd[1]: Started Time & Date Service.
Dec 16 12:51:24 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=11/SEGV
[...]
Dec 16 12:53:47 TREND-24-AF-7A systemd-resolved[2591]: Assertion 'DNS_TRANSACTION_IS_LIVE(q->state)' failed at src/resolve/resolved-dns-query.c:520, function dns_query_complete(). Aborting.
Dec 16 12:53:47 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=6/ABRT
[ Test Plan ]
The exact steps to reproduce this issue are still not known.
But we see this crash only in Static IP Addressing mode enabled, where systemd-resolved is enabled for LLMNR service.
But we were not able to see this crash in DHCP mode.
Steps to reproduce:
1) Powercycle the device.
2) Soft-reboot.
[ Where problems could occur ]
The patch[1] simply disables the timer event source for a DNS query when the struct representing that query is free'd. I cannot see any realistic regression potential, because if the timer event fired on the DNS query after it has been free'd, then that would be this bug. I.e. no working code should be relying on the timer event source still being around after the query is free'd.
[1] https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b |
[ Impact ]
The continuous systemd-resolved crashes delay/hang the device startup.
And this leads to unresponsive devices in the system. Specifically, the crash looks like:
Dec 16 12:51:21 TREND-24-AF-7A systemd[1]: Started Time & Date Service.
Dec 16 12:51:24 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=11/SEGV
[...]
Dec 16 12:53:47 TREND-24-AF-7A systemd-resolved[2591]: Assertion 'DNS_TRANSACTION_IS_LIVE(q->state)' failed at src/resolve/resolved-dns-query.c:520, function dns_query_complete(). Aborting.
Dec 16 12:53:47 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=6/ABRT
[ Test Plan ]
The exact steps to reproduce this issue are still not known.
But we see this crash only in Static IP Addressing mode enabled, where systemd-resolved is enabled for LLMNR service.
But we were not able to see this crash in DHCP mode.
Steps to reproduce:
1) Powercycle the device.
2) Soft-reboot.
It was also pointed out by Brian Murray that this error in the Ubuntu error tracker is likely the same bug: https://errors.ubuntu.com/problem/3cb08ae5efaa4d8c6ce992f7cebd2751ae3f168f. Therefore, we would expect to stop seeing this error in the tracker as a result of this patch.
[ Where problems could occur ]
The patch[1] simply disables the timer event source for a DNS query when the struct representing that query is free'd. I cannot see any realistic regression potential, because if the timer event fired on the DNS query after it has been free'd, then that would be this bug. I.e. no working code should be relying on the timer event source still being around after the query is free'd.
[1] https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b |
|
| 2023-05-22 20:38:16 |
Brian Murray |
systemd (Ubuntu Focal): status |
Triaged |
Fix Committed |
|
| 2023-05-22 20:38:16 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-05-22 20:38:24 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2023-05-22 20:38:26 |
Brian Murray |
tags |
|
verification-needed verification-needed-focal |
|
| 2023-05-24 00:30:29 |
Kenyon Ralph |
bug |
|
|
added subscriber Kenyon Ralph |
| 2023-05-25 21:32:22 |
Bugra Aydogar |
tags |
verification-needed verification-needed-focal |
verification-done-focal |
|
| 2023-06-14 13:53:35 |
Robie Basak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-06-14 13:53:35 |
Launchpad Janitor |
systemd (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
