CVE-2025-40060: coresight: trbe: Return NULL pointer for allocation failures
Noroxi assessment
Priority: Monitor (action score 0/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.22% (FIRST EPSS).
- Fixed version: Linux Linux 296da78494633e1ab5e2e74173a9c8683b04aa6b, 8a55c161f7f9c1aa1c70611b39830d51c83ef36d, 9768536f82600a05ce901e31ccfabd92c027ff71.
Low priority for now. Upgrade to Linux Linux 296da78494633e1ab5e2e74173a9c8683b04aa6b, 8a55c161f7f9c1aa1c70611b39830d51c83ef36d, 9768536f82600a05ce901e31ccfabd92c027ff71 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: coresight: trbe: Return NULL pointer for allocation failures When the TRBE driver fails to allocate a buffer, it currently returns the error code "-ENOMEM". However, the caller etm_setup_aux() only checks for a NULL pointer, so it misses the error. As a result, the driver continues and eventually causes a kernel panic. Fix this by returning a NULL pointer from arm_trbe_alloc_buffer() on allocation failures. This allows that the callers can properly handle the failure.
- Published
- Oct 28, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
—
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
- 3fbf7f011f2426dac8c982f1d2ef469a7959a524 and later · before cef047e0a55cb07906fcaae99170f19a9c0bb6c2affected · git
- 3fbf7f011f2426dac8c982f1d2ef469a7959a524 and later · before fe53a726d5edf864e80b490780cc135fc1adece9affected · git
- 3fbf7f011f2426dac8c982f1d2ef469a7959a524 and later · before 9768536f82600a05ce901e31ccfabd92c027ff71affected · git
- 3fbf7f011f2426dac8c982f1d2ef469a7959a524 and later · before 296da78494633e1ab5e2e74173a9c8683b04aa6baffected · git
- 3fbf7f011f2426dac8c982f1d2ef469a7959a524 and later · before f505a165f1c7cd37b4cb6952042a5984693a4067affected · git
- 3fbf7f011f2426dac8c982f1d2ef469a7959a524 and later · before 8a55c161f7f9c1aa1c70611b39830d51c83ef36daffected · git
- before 5.13not affected · semver
- 5.15.195 and later · up to and including 5.15.*not affected · semver
- 6.1.156 and later · up to and including 6.1.*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.158-1 | 6.1.158-1 |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40058Oct 28, 2025 · iommu/vt-d: Disallow dirty tracking if incoherent page walk35Monitor
- ← EarlierCVE-2025-40059Oct 28, 2025 · coresight: Fix incorrect handling for return value of devm_kzalloc0Monitor
- Later →CVE-2025-40061Oct 28, 2025 · RDMA/rxe: Fix race in do_task() when draining31Monitor
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 | 296da78494633e1ab5e2e74173a9c8683b04aa6b | Vendor (CNA) |
| Linux Linux | 8a55c161f7f9c1aa1c70611b39830d51c83ef36d | Vendor (CNA) |
| Linux Linux | 9768536f82600a05ce901e31ccfabd92c027ff71 | Vendor (CNA) |
| Linux Linux | cef047e0a55cb07906fcaae99170f19a9c0bb6c2 | Vendor (CNA) |
| Linux Linux | f505a165f1c7cd37b4cb6952042a5984693a4067 | Vendor (CNA) |
| Linux Linux | fe53a726d5edf864e80b490780cc135fc1adece9 | Vendor (CNA) |
| debian:linux | 6.1.158-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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (5 more)Show less
- git.kernel.org/stable/c/8a55c161f7f9c1aa1c70611b39830d51c83ef36d
- git.kernel.org/stable/c/9768536f82600a05ce901e31ccfabd92c027ff71
- git.kernel.org/stable/c/cef047e0a55cb07906fcaae99170f19a9c0bb6c2
- git.kernel.org/stable/c/f505a165f1c7cd37b4cb6952042a5984693a4067
- git.kernel.org/stable/c/fe53a726d5edf864e80b490780cc135fc1adece9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.