CVE-2025-21804: PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 24576899c49509c0d533bcf569139f691d8f7af7, 2c54b9fca1755e80a343ccfde0652dc5ea4744b2, 2d2da5a4c1b4509f6f7e5a8db015cd420144beb4.
Low priority for now. Upgrade to Linux Linux 24576899c49509c0d533bcf569139f691d8f7af7, 2c54b9fca1755e80a343ccfde0652dc5ea4744b2, 2d2da5a4c1b4509f6f7e5a8db015cd420144beb4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region() The rcar_pcie_parse_outbound_ranges() uses the devm_request_mem_region() macro to request a needed resource. A string variable that lives on the stack is then used to store a dynamically computed resource name, which is then passed on as one of the macro arguments. This can lead to undefined behavior. Depending on the current contents of the memory, the manifestations of errors may vary. One possible output may be as follows: $ cat /proc/iomem 30000000-37ffffff : 38000000-3fffffff : Sometimes, garbage may appear after the colon. In very rare cases, if no NULL-terminator is found in memory, the system might crash because the string iterator will overrun which can lead to access of unmapped memory above the stack. Thus, fix this by replacing outbound_name with the name of the previously requested resource. With the changes applied, the output will be as follows: $ cat /proc/iomem 30000000-37ffffff : memory2 38000000-3fffffff : memory3 [kwilczynski: commit log]
- Published
- Feb 27, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.1
- 1.6 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.8 and later · before 5.10.235
- linux linux kernel5.11 and later · before 5.15.179
- linux linux kernel5.16 and later · before 6.1.129
- linux linux kernel6.2 and later · before 6.6.76
- linux linux kernel6.7 and later · before 6.12.13
- linux linux kernel6.13 and later · before 6.13.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.8affected
- 2a6d0d63d99956a66f6605832f11755d74a41951 and later · before 7a47e14c5fb0b6dba7073be7b0119fb8fe864e01affected · git
- 2a6d0d63d99956a66f6605832f11755d74a41951 and later · before 6987e021b64cbb49981d140bb72d9d1466f191c4affected · git
- 2a6d0d63d99956a66f6605832f11755d74a41951 and later · before 24576899c49509c0d533bcf569139f691d8f7af7affected · git
- 2a6d0d63d99956a66f6605832f11755d74a41951 and later · before 2c54b9fca1755e80a343ccfde0652dc5ea4744b2affected · git
- 2a6d0d63d99956a66f6605832f11755d74a41951 and later · before 9ff46b0bfeb6e0724a4ace015aa7a0b887cdb7c1affected · git
- 2a6d0d63d99956a66f6605832f11755d74a41951 and later · before 44708208c2a4b828a57a2abe7799c9d3962e7eaaaffected · git
- 2a6d0d63d99956a66f6605832f11755d74a41951 and later · before 2d2da5a4c1b4509f6f7e5a8db015cd420144beb4affected · git
- before 5.8not affected · semver
- 5.10.235 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.129-1 | 6.1.129-1 |
| Debian:13 | linux | before 6.12.13-1 | 6.12.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-21800Feb 27, 2025 · net/mlx5: HWS, fix definer's HWS_SET32 macro for negative offset31Monitor
- ← EarlierCVE-2025-21803Feb 27, 2025 · LoongArch: Fix warnings during S3 suspend22Monitor
- Later →CVE-2025-21805Feb 27, 2025 · RDMA/rtrs: Add missing deinit() call22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 24576899c49509c0d533bcf569139f691d8f7af7 | Vendor (CNA) |
| Linux Linux | 2c54b9fca1755e80a343ccfde0652dc5ea4744b2 | Vendor (CNA) |
| Linux Linux | 2d2da5a4c1b4509f6f7e5a8db015cd420144beb4 | Vendor (CNA) |
| Linux Linux | 44708208c2a4b828a57a2abe7799c9d3962e7eaa | Vendor (CNA) |
| Linux Linux | 6987e021b64cbb49981d140bb72d9d1466f191c4 | Vendor (CNA) |
| Linux Linux | 7a47e14c5fb0b6dba7073be7b0119fb8fe864e01 | Vendor (CNA) |
| Linux Linux | 9ff46b0bfeb6e0724a4ace015aa7a0b887cdb7c1 | Vendor (CNA) |
| debian:linux | 6.1.129-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/2c54b9fca1755e80a343ccfde0652dc5ea4744b2
- git.kernel.org/stable/c/2d2da5a4c1b4509f6f7e5a8db015cd420144beb4
- git.kernel.org/stable/c/44708208c2a4b828a57a2abe7799c9d3962e7eaa
- git.kernel.org/stable/c/6987e021b64cbb49981d140bb72d9d1466f191c4
- git.kernel.org/stable/c/7a47e14c5fb0b6dba7073be7b0119fb8fe864e01
- git.kernel.org/stable/c/9ff46b0bfeb6e0724a4ace015aa7a0b887cdb7c1
- lists.debian.org/debian-lts-announce/2025/03/msg00028.html
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.