In the Linux kernel, the following vulnerability has been resolved:
devlink: fix xa_alloc_cyclic() error handling
In case of returning 1 from xa_alloc_cyclic() (wrapping) ERR_PTR(1) will
be returned, which will cause IS_ERR() to be false. Which can lead to
dereference not allocated pointer (rel).
Fix it by checking if err is lower than zero.
This wasn't found in real usecase, only noticed. Credit to Pierre.
Security readout for executives and security teams
Plain-English summary
CVE-2025-22017 is a Linux kernel devlink bug in error handling. Under a wraparound return case, code could treat an invalid pointer as valid and dereference it. The source says it was noticed during review, not found in real use. Severity and CVSS are not provided.
Executive priority
Treat as a kernel maintenance item until severity is clarified. It should enter normal vulnerability management, with higher priority for internet-facing or high-availability Linux infrastructure, but the supplied evidence does not justify emergency response.
Technical view
The issue is in devlink handling of xa_alloc_cyclic(). A return value of 1 during wrapping could become ERR_PTR(1), while IS_ERR() would not flag it as an error. That can lead to dereferencing a pointer that was not allocated. The fix checks for errors lower than zero.
Likely exposure
Exposure appears limited to Linux kernels containing the affected devlink code path. The CVE data lists Linux kernel versions and stable commit references, but does not provide distribution package names, configurations, or deployment prerequisites.
Exploitation context
There is no cited evidence of active exploitation. The CVE is not marked KEV, and the description says the issue was not found in a real use case, only noticed. Practical exploitability is not established in the provided sources.
Researcher notes
Key uncertainty is exploitability. The root cause is a devlink xa_alloc_cyclic() wraparound handling flaw leading to possible invalid pointer dereference. Source evidence provides stable commit links but no CVSS, CWE, exploit report, or distribution-specific fixed versions.
Mitigation direction
Track Linux or distribution kernel updates that include the referenced stable commits.
Prioritize affected systems where kernel devlink functionality is relevant.
Check vendor guidance before applying non-distribution kernel changes.
Plan reboot or live-patch procedures according to normal kernel update policy.
Validation and detection
Inventory deployed Linux kernel versions across servers, appliances, and container hosts.
Compare kernel versions with the CVE affected entries and vendor advisories.
Verify whether kernel packages include one of the referenced stable commits.
Document any systems deferred from update and their compensating controls.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-22017 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Apr 8, 2025, 08:18 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.