IRONSMITHINTEL
HIGHCVSS7.8
|
Actively Exploited
|CISA KEV|CVE-2023-0386|Auth: low — authenticated user|Reboot: required|Manual only

Linux Kernel Improper Ownership Management Vulnerability (CVE-2023-0386)

Linux Kernel contains an improper ownership management vulnerability, where unauthorized access to the execution of the setuid file with capabilities was found in the Linux kernel’s OverlayFS subsystem in how a user copies a capable file from a nosuid mount into another mount. This uid mapping bug allows a local user to escalate their privileges on the system.

Published Mar 22, 2023 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A local attacker, with a low-privilege account, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2025-07-08 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-282) (CWE-282) vulnerability in Linux Kernel. A flaw was found in the Linux kernel, where unauthorized access to the execution of the setuid file with capabilities was found in the Linux kernel’s OverlayFS subsystem in how a user copies a capable file from a nosuid mount into another mount. This uid mapping bug allows a local user to escalate their privileges on the system. Exploitation requires local access, low attack complexity, a low-privilege authenticated account, and no user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

●IT Security
●Running debian linux: 10.0; h300s firmware: -; h500s firmware: -; h700s firmware: -; h410s firmware: -; h410c firmware: -; ubuntu linux: 18.04, 20.04, 22.04; linux kernel: 5.11 ≤ v < 5.15.91, 5.16 ≤ v < 6.1.9, 6.2
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2025-06-17 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2025-07-08.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for general installs in scope.
2
Apply the vendor security update referenced in CVE-2023-0386's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2023-0386↗ MSRC Advisory↗ NVD↗ Vendor Advisory