Kernel-memory disclosure or crash via dangling resource name
Published Feb 27, 2025 · Updated Aug 5, 2026
Memory-safety failure in Linux kernel R-Car PCIe endpoint support allows local users to disclose kernel memory or crash the system. rcar_pcie_parse_outbound_ranges() passes the stack-backed outbound_name buffer to devm_request_mem_region(), leaving resource entries with a dangling name pointer after the function returns. Reading the world-readable /proc/iomem on an affected R-Car endpoint dereferences that pointer, exposing stale stack data or overrunning into unmapped memory and crashing the kernel.
Summary
What happened
Memory-safety failure in Linux kernel R-Car PCIe endpoint support allows local users to disclose kernel memory or crash the system. rcar_pcie_parse_outbound_ranges() passes the stack-backed outbound_name buffer to devm_request_mem_region(), leaving resource entries with a dangling name pointer after the function returns. Reading the world-readable /proc/iomem on an affected R-Car endpoint dereferences that pointer, exposing stale stack data or overrunning into unmapped memory and crashing the kernel.
The record
- CVE
- CVE-2025-21804
- Published
- Feb 27, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2a6d0d63d99956a66f6605832f11755d74a41951 <24576899c49509c0d533bcf569139f691d8f7af7
- Affected versionversion=2a6d0d63d99956a66f6605832f11755d74a41951 <2c54b9fca1755e80a343ccfde0652dc5ea4744b2
- Affected versionversion=2a6d0d63d99956a66f6605832f11755d74a41951 <2d2da5a4c1b4509f6f7e5a8db015cd420144beb4
- Affected versionversion=2a6d0d63d99956a66f6605832f11755d74a41951 <44708208c2a4b828a57a2abe7799c9d3962e7eaa
- Affected versionversion=2a6d0d63d99956a66f6605832f11755d74a41951 <6987e021b64cbb49981d140bb72d9d1466f191c4
- Affected versionversion=2a6d0d63d99956a66f6605832f11755d74a41951 <7a47e14c5fb0b6dba7073be7b0119fb8fe864e01
- Affected versionversion=2a6d0d63d99956a66f6605832f11755d74a41951 <9ff46b0bfeb6e0724a4ace015aa7a0b887cdb7c1
- Affected versionversion=5.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo