FEDORA-2021-2a6ba64260 created by zbyszek 3 months ago for Fedora 34
stable
  • Various minor documentation and correctness fixes.
  • CVE-2021-33910, #1984020: an unchecked stack allocation could be used to crash systemd and cause the system to reboot by creating a very long fuse mountpoint path.

No need to log out or reboot.

How to install

sudo dnf upgrade --advisory=FEDORA-2021-2a6ba64260

This update has been submitted for testing by zbyszek.

3 months ago

This update's test gating status has been changed to 'failed'.

3 months ago

This update's test gating status has been changed to 'waiting'.

3 months ago

This update's test gating status has been changed to 'failed'.

3 months ago

This update's test gating status has been changed to 'passed'.

3 months ago
User Icon imabug provided feedback 3 months ago
karma

This update has been pushed to testing.

3 months ago
User Icon bojan commented & provided feedback 3 months ago
karma

Works.

This update can be pushed to stable now if the maintainer wishes

3 months ago
User Icon atim provided feedback 3 months ago
karma

This update has been submitted for stable by bodhi.

3 months ago
User Icon ibims provided feedback 3 months ago
karma

This update has been pushed to stable.

3 months ago
User Icon forgems commented & provided feedback 3 months ago
karma

After today's update to this version, User Manager doesn't start on Fedora 34

Jul 22 12:32:27 thinkpad systemd[1934]: PAM failed: Authentication failure
Jul 22 12:32:27 thinkpad systemd[1934]: user@42.service: Failed to set up PAM session: Operation not permitted
Jul 22 12:32:27 thinkpad systemd[1934]: user@42.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Jul 22 12:32:27 thinkpad systemd[1]: user@42.service: Main process exited, code=exited, status=224/PAM
Jul 22 12:32:27 thinkpad systemd[1]: user@42.service: Failed with result 'exit-code'.
Jul 22 12:32:27 thinkpad systemd[1]: Failed to start User Manager for UID 42.
Jul 22 12:32:40 thinkpad systemd[2565]: PAM failed: Authentication failure
Jul 22 12:32:40 thinkpad systemd[2565]: user@1000.service: Failed to set up PAM session: Operation not permitted
Jul 22 12:32:40 thinkpad systemd[2565]: user@1000.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Jul 22 12:32:40 thinkpad systemd[1]: user@1000.service: Main process exited, code=exited, status=224/PAM
Jul 22 12:32:40 thinkpad systemd[1]: user@1000.service: Failed with result 'exit-code'.
Jul 22 12:32:40 thinkpad systemd[1]: Failed to start User Manager for UID 1000.
User Icon zbyszek commented & provided feedback 3 months ago

@forgems: please open a new bug. This update is already stable. I suspect this might be somehow related to https://github.com/systemd/systemd-stable/commit/0af5a8921f.


Please login to add feedback.

Metadata
Type
security
Severity
high
Karma
3
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
14 days
Dates
submitted
3 months ago
in testing
3 months ago
in stable
3 months ago
BZ#1984020 CVE-2021-33910 systemd: uncontrolled allocation on the stack in function unit_name_path_escape leads to crash [fedora-all]
0
0

Automated Test Results

Test Cases

0 0 Test Case base service manipulation
0 2 Test Case base services start
0 2 Test Case base shutdown/reboot