LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22046: uprobes/x86: Harden uretprobe syscall trampoline check

In the Linux kernel, the following vulnerability has been resolved: uprobes/x86: Harden uretprobe syscall trampoline check Jann reported a possible issue when trampoline_check_ip returns address near the bottom of the address space that is allowed to call into the syscall if uretprobes are not set up: https://lore.kernel.org/bpf/202502081235.5A6F352985@keescook/T/#m9d416df341b8fbc11737dacbcd29f0054413cbbf Though the mmap minimum address restrictions will typically prevent creating mappings there, let's make sure uretprobe syscall checks for that.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2025-22046 is a Linux kernel hardening fix around x86 return probes, called uretprobes. The report describes a possible incorrect syscall trampoline address check near the bottom of user address space. Normal mmap minimum-address restrictions usually reduce exposure, but affected kernels should take the upstream stable fix through their distribution or kernel update path.

Executive priority

Treat as a routine kernel maintenance item unless vendor advisories rate your distribution build higher. No source evidence indicates active exploitation, but kernel issues still deserve timely patching on shared, multi-user, and internet-facing infrastructure.

Technical view

The Linux kernel x86 uprobes code hardened trampoline_check_ip handling for uretprobe syscall checks. The issue concerns an address near the bottom of the address space being accepted when uretprobes are not set up. The CVE source lists Linux kernel affected ranges and multiple stable commit references, but provides no CVSS, CWE, or exploit details.

Likely exposure

Exposure is limited to systems running affected Linux kernel versions or downstream builds that include the vulnerable x86 uprobes behavior. Distribution kernels need vendor-specific mapping because the CVE bundle cites upstream versions and stable commits, not package names.

Exploitation context

The source bundle does not cite active exploitation, public exploit use, or CISA KEV listing. It describes a possible issue reported to kernel maintainers and notes mmap minimum-address restrictions will typically prevent creating mappings in the relevant low address area.

Researcher notes

The record is evidence-light: no CVSS, CWE, exploit narrative, or distro package matrix is provided. Focus validation on upstream commit presence, distro backports, affected x86 kernel builds, and whether local policy weakens low-address mmap protections.

Mitigation direction

  • Update affected Linux kernels through the OS vendor or upstream stable channel.
  • Prioritize systems that allow untrusted local users or developer workloads.
  • Keep mmap minimum-address restrictions enabled unless vendor guidance says otherwise.
  • Track distribution advisories that map this CVE to package versions.

Validation and detection

  • Inventory running kernel versions across Linux hosts.
  • Compare kernels against vendor advisories for CVE-2025-22046.
  • Confirm patched kernels include the referenced upstream stable fix.
  • Review local hardening for mmap minimum address restrictions.
Prepared
Confidence
medium
Sources
6

Public sources used

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-22046 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxff474a78cef5cb5f32be52fe25b78441327a2e7c, ff474a78cef5cb5f32be52fe25b78441327a2e7c, ff474a78cef5cb5f32be52fe25b78441327a2e7c, ff474a78cef5cb5f32be52fe25b78441327a2e7cunaffected
LinuxLinux6.11, 0, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.