Bug 2555246 (CVE-2026-98847)

Summary:	CVE-2026-98847 kernel: rtc: spear: initialize IRQ state before requesting alarm IRQ
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	akhatavk, aos-team-art-private, asdas, dpaolell, jdelft, jupierce, lgarciaa, mbiarnes, ppalepu, ppostler, prdhamdh, rhel-process-autobot, sghai, sidsharm, suppawar, vlaad, watson-tool-maintainers
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in the Linux kernel's SPEAr Real-Time Clock (RTC) driver. The driver requests and enables an alarm interrupt before completing device initialization, specifically prior to setting up the memory-mapped I/O (MMIO) address and spinlock. If an interrupt triggers while device probing is in progress, the handler attempts to run with uninitialized resources. This race condition can cause the system to crash, leading to a Denial of Service (DoS).	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-10-18 16:04:26 UTC

In the Linux kernel, the following vulnerability has been resolved:

rtc: spear: initialize IRQ state before requesting alarm IRQ

devm_request_irq() enables the interrupt before it returns, so the handler
may run while probe is still initializing the device. Initialize the MMIO
address and spinlock before requesting the alarm IRQ.

Comment 1 Mauro Matteo Cascella 2026-10-23 22:10:27 UTC

Upstream advisory:
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-98847.mbox