Skip to main content
CVE-2025-38499VulnerabilityPublished Updated

SUSE · security update for kernel

Affects SUSESource GCVE Database

0

Not known to be exploited · fixed in 5.15.0-1102.111~20.04.1 : patch SUSE soon.

Data as of 25 Oct 2026, 19:02 UTC

Severity
High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.15.0-1102.111~20.04.1, 5.15.0-1097.106~20.04.1, 5.15.0-1097.104~20.04.1 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
SUSE Product Security Team SUSEAffected
  • <5.15.0-1097.104~20.04.1
  • <5.15.0-1102.111~20.04.1
  • <5.15.0-1097.106~20.04.1
  • <5.15.0-163.173~20.04.1
  • <5.15.0-1091.94~20.04.1
Fixed in
  • 5.15.0-1097.104~20.04.1
  • 5.15.0-1102.111~20.04.1
  • 5.15.0-1097.106~20.04.1
  • 5.15.0-163.173~20.04.1
  • 5.15.0-1091.94~20.04.1

AI-suggested

A security update patch is available from Red Hat and must be applied. The system requires a reboot for the update to take effect. Users should follow the vendor's official guidance at https://access.redhat.com/articles/11258 to apply the update. No additional mitigation steps are indicated by the vendor advisory.

Description

A security vulnerability in the Linux kernel's clone_private_mnt() function was identified and fixed. The flaw was due to missing verification that the caller has the CAP_SYS_ADMIN capability in the appropriate user namespace, which could allow unauthorized mount namespace operations. This issue affects Red Hat Enterprise Linux 9 and related variants. A patch is available and requires a system reboot to take effect.

References

Community reviews

Loading reviews…