Bug 2336530

Summary: plymouthd crashes nondeterministically on boot with segmentation violation
Product: [Fedora] Fedora Reporter: BZ <bgz>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 41CC: gnome-sig, hdegoede, rstrode
Target Milestone: ---Keywords: Reopened, Security
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-07-03 09:34:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Output of coredumpctl info none

Description BZ 2025-01-09 11:07:50 UTC 
In one case out of approximately 12 system boots after upgrading to Fedora 41, plymouthd crashed with a segmentation violation, terminating the boot process. A hard restart/reboot then worked normally, as have subsequent attempts. I'll attach the output of 'coredumpctl info' after posting the bug.

Since nondeterministic segmentation violations are typically caused by potentially exploitable memory errors, I've tentatively marked this as a possible security issue. I have the binary coredump file so can provide that, but I'm not sure if it might contain sensitive information, so didn't want to just attach it for all the world to see. Just let me know.

This may or may not be related to https://bugzilla.redhat.com/show_bug.cgi?id=2302344 which also seems to involve a plymouth crash while doing something with the splash screen, but there don't seem to be any similarities beyond that.

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1. Boot the system
2.
3.
Actual Results:  
An ugly crash dump gets written across the console and the boot process hangs

Expected Results:  
Normal boot

System is a Dell Latitude laptop and was upgraded from Fedora 40 to Fedora 41 about a week ago. No problems until this particular crash.
Comment 1 BZ 2025-01-09 11:08:51 UTC 
Created attachment 2065281 [details]
Output of coredumpctl info
Comment 2 Hans de Goede 2025-06-18 10:35:14 UTC 
Thank you for your bugreport I think that I know what is going on and I hope I'll be able to provide a fix soon.

This is also being tracked in bug 2368186, I'm marking this bug as a duplicate of that bug.

*** This bug has been marked as a duplicate of bug 2368186 ***
Comment 3 Hans de Goede 2025-06-19 20:35:08 UTC 
I accidentally mixed this bug up with another bug. This one is not a duplicate of 2368186, so lets re-open it, sorry.
Comment 4 Hans de Goede 2025-06-19 20:54:38 UTC 
It does look like this might very well be a dup of bug 2302344 though. Unfortunately we don't have a fix for that one yet.
Comment 5 Hans de Goede 2025-07-03 09:34:15 UTC 
Marking as a duplicate of bug 2302344. Note unfortunately we don't have a fix for that / this bug yet.

*** This bug has been marked as a duplicate of bug 2302344 ***