CVE-2025-38152: remoteproc: core: Clear table_sz when rproc_shutdown
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.27% (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 068f6648ff5b0c7adeb6c363fae7fb188aa178fa, 2df19f5f6f72da6f6ebab7cdb3a3b9f7686bb476, 6e66bca8cd51ebedd5d32426906a38e4a3c69c5f; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 5.15.180.1-1.
Low priority for now. Upgrade to Linux Linux 068f6648ff5b0c7adeb6c363fae7fb188aa178fa, 2df19f5f6f72da6f6ebab7cdb3a3b9f7686bb476, 6e66bca8cd51ebedd5d32426906a38e4a3c69c5f; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 5.15.180.1-1 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: remoteproc: core: Clear table_sz when rproc_shutdown There is case as below could trigger kernel dump: Use U-Boot to start remote processor(rproc) with resource table published to a fixed address by rproc. After Kernel boots up, stop the rproc, load a new firmware which doesn't have resource table ,and start rproc. When starting rproc with a firmware not have resource table, `memcpy(loaded_table, rproc->cached_table, rproc->table_sz)` will trigger dump, because rproc->cache_table is set to NULL during the last stop operation, but rproc->table_sz is still valid. This issue is found on i.MX8MP and i.MX9. Dump as below: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 4k pages, 48-bit VAs, pgdp=000000010af63000 [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Modules linked in: CPU: 2 UID: 0 PID: 1060 Comm: sh Not tainted 6.14.0-rc7-next-20250317-dirty #38 Hardware name: NXP i.MX8MPlus EVK board (DT) pstate: a0000005 (NzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __pi_memcpy_generic+0x110/0x22c lr : rproc_start+0x88/0x1e0 Call trace: __pi_memcpy_generic+0x110/0x22c (P) rproc_boot+0x198/0x57c state_store+0x40/0x104 dev_attr_store+0x18/0x2c sysfs_kf_write+0x7c/0x94 kernfs_fop_write_iter+0x120/0x1cc vfs_write+0x240/0x378 ksys_write+0x70/0x108 __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x10c el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x30/0xcc el0t_64_sync_handler+0x10c/0x138 el0t_64_sync+0x198/0x19c Clear rproc->table_sz to address the issue.
- Published
- Apr 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 19th 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%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.13 and later · before 5.15.180
- linux linux kernel5.16 and later · before 6.1.134
- linux linux kernel6.2 and later · before 6.6.87
- linux linux kernel6.7 and later · before 6.12.23
- linux linux kernel6.13 and later · before 6.13.11
- linux linux kernel6.14 and later · before 6.14.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.13affected
- 9dc9507f1880fb6225e3e058cb5219b152cbf198 and later · before 6e66bca8cd51ebedd5d32426906a38e4a3c69c5faffected · git
- 9dc9507f1880fb6225e3e058cb5219b152cbf198 and later · before e6015ca453b82ec54aec9682dcc38773948fcc48affected · git
- 9dc9507f1880fb6225e3e058cb5219b152cbf198 and later · before 7c6bb82a6f3da6ab2d3fbea03901482231708b98affected · git
- 9dc9507f1880fb6225e3e058cb5219b152cbf198 and later · before 2df19f5f6f72da6f6ebab7cdb3a3b9f7686bb476affected · git
- 9dc9507f1880fb6225e3e058cb5219b152cbf198 and later · before 8e0fd2a3b9852ac3cf540edb06ccc0153b38b5afaffected · git
- 9dc9507f1880fb6225e3e058cb5219b152cbf198 and later · before 068f6648ff5b0c7adeb6c363fae7fb188aa178faaffected · git
- 9dc9507f1880fb6225e3e058cb5219b152cbf198 and later · before efdde3d73ab25cef4ff2d06783b0aad8b093c0e4affected · git
- before 5.13not affected · semver
- 5.15.180 and later · up to and including 5.15.*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.135-1 | 6.1.135-1 |
| Debian:13 | linux | before 6.12.25-1 | 6.12.25-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-38049Apr 18, 2025 · x86/resctrl: Fix allocation of cleanest CLOSID on platforms with no monitors22Monitor
- ← EarlierCVE-2025-38104Apr 18, 2025 · drm/amdgpu: Replace Mutex with Spinlock for RLCG register access to avoid Priority Inversion in SRIOV18Monitor
- Later →CVE-2025-38240Apr 18, 2025 · drm/mediatek: dp: drm_err => dev_err in HPD path to avoid NULL ptr22Monitor
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 | 068f6648ff5b0c7adeb6c363fae7fb188aa178fa | Vendor (CNA) |
| Linux Linux | 2df19f5f6f72da6f6ebab7cdb3a3b9f7686bb476 | Vendor (CNA) |
| Linux Linux | 6e66bca8cd51ebedd5d32426906a38e4a3c69c5f | Vendor (CNA) |
| Linux Linux | 7c6bb82a6f3da6ab2d3fbea03901482231708b98 | Vendor (CNA) |
| Linux Linux | 8e0fd2a3b9852ac3cf540edb06ccc0153b38b5af | Vendor (CNA) |
| Linux Linux | e6015ca453b82ec54aec9682dcc38773948fcc48 | Vendor (CNA) |
| Linux Linux | efdde3d73ab25cef4ff2d06783b0aad8b093c0e4 | Vendor (CNA) |
| azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 | 5.15.180.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.135-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 (7 more)Show less
- git.kernel.org/stable/c/2df19f5f6f72da6f6ebab7cdb3a3b9f7686bb476
- git.kernel.org/stable/c/6e66bca8cd51ebedd5d32426906a38e4a3c69c5f
- git.kernel.org/stable/c/7c6bb82a6f3da6ab2d3fbea03901482231708b98
- git.kernel.org/stable/c/8e0fd2a3b9852ac3cf540edb06ccc0153b38b5af
- git.kernel.org/stable/c/e6015ca453b82ec54aec9682dcc38773948fcc48
- git.kernel.org/stable/c/efdde3d73ab25cef4ff2d06783b0aad8b093c0e4
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.