CVE-2025-40076: PCI: rcar-host: Pass proper IRQ domain to generic_handle_domain_irq()

Published Oct 28, 2025
·
Updated

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

PCI: rcar-host: Pass proper IRQ domain to generichandledomainirq()

Starting with commit dd26c1a23fd5 ("PCI: rcar-host: Switch to msicreateparentirqdomain()"), the MSI parent IRQ domain is NULL because the object of type struct irqdomaininfo passed to:

msicreateparentirqdomain() -> irqdomaininstantiate()() -> irqdomaininstantiate()

has no reference to the parent IRQ domain. Using msi->domain->parent as an argument for generichandledomainirq() leads to below error:

"Unable to handle kernel NULL pointer dereference at virtual address"

This error was identified while switching the upcoming RZ/G3S PCIe host controller driver to msicreateparentirqdomain() (which was using a similar pattern to handle MSIs (see link section)), but it was not tested on hardware using the pcie-rcar-host controller driver due to lack of hardware.

[mani: reworded subject and description]

Affected Software

1 affected component
Linux kernel pcie-rcar-host

Event History

Oct 28, 2025
CVE Published
via MITRE·11:48 AM
Data Sourced
via MITRE·11:48 AM
Description
Data Sourced
via NVD·12:15 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-40076?

CVE-2025-40076 is classified as a medium severity vulnerability in the Linux kernel.

2

How do I fix CVE-2025-40076?

To fix CVE-2025-40076, update to a version of the Linux kernel that includes the patch for this vulnerability.

3

What impact does CVE-2025-40076 have on my system?

CVE-2025-40076 may lead to improper handling of interrupts, potentially causing system instability.

4

Which versions of the Linux kernel are affected by CVE-2025-40076?

CVE-2025-40076 affects Linux kernel versions starting from commit dd26c1a23fd5.

5

Is there a workaround for CVE-2025-40076?

There is no known workaround for CVE-2025-40076; updating the kernel is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203