Description
In the Linux kernel, the following vulnerability has been resolved:

memfd: deny writeable mappings when implying SEAL_WRITE

When SEAL_EXEC is added, SEAL_WRITE is implied to make W^X. But the
implied seal is set after the check that makes sure the memfd can not have
any writable mappings. This means one can use SEAL_EXEC to apply
SEAL_WRITE while having writeable mappings.

This breaks the contract that SEAL_WRITE provides and can be used by an
attacker to pass a memfd that appears to be write sealed but can still be
modified arbitrarily.

Fix this by adding the implied seals before the call for
mapping_deny_writable() is done.
Published: 2026-07-19
Score: 8.4 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In the Linux kernel the memfd mechanism incorrectly applies SEAL_WRITE when a process sets SEAL_EXEC. Because the implied seal is added after the check that forbids writable mappings, the vulnerability allows a memfd to appear write‑sealed while still permitting writable mappings. This breaks the contract that SEAL_WRITE provides and enables an attacker to modify the contents of a supposedly write‑sealed memory file. Based on the description, it is inferred that this could enable code injection or privilege escalation.

Affected Systems

All Linux kernel builds that have not incorporated the recent patch are potentially impacted. The vulnerability applies to the Linux kernel as a whole; no specific kernel version range is cited, so any unpatched kernel can be exploited.

Risk and Exploitability

The CVSS score of 8.4 indicates a high‑severity local vulnerability. The EPSS score of less than 1% suggests a low probability of immediate public exploitation, and the flaw is not listed in the CISA KEV catalog. The vulnerability arises from a misordered check where SEAL_WRITE is applied after denying writable mappings, allowing an attacker who can create a memfd and issue the SEAL_EXEC flag to keep writable mappings while the memfd claims to be write‑sealed. This permits arbitrary memory modification or execution in a local context, potentially enabling privilege escalation or other local exploits.

Generated by OpenCVE AI on August 4, 2026 at 06:34 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the kernel patch that adds implied seals before calling mapping_deny_writable(), ensuring SEAL_WRITE is enforced before writable mappings are checked.
  • If an immediate kernel upgrade cannot be performed, restrict or monitor the use of memfd_create and fcntl SEAL_EXEC by revoking unnecessary capabilities or applying SELinux/AppArmor policies.
  • Enable kernel audit logging for memfd operations and fcntl calls to detect anomalous writable mappings and potential exploitation attempts.

Generated by OpenCVE AI on August 4, 2026 at 06:34 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
History

Sun, 26 Jul 2026 08:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362

Wed, 22 Jul 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-266
References
Metrics threat_severity

None

threat_severity

Important


Tue, 21 Jul 2026 23:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362

Mon, 20 Jul 2026 14:45:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.4, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N'}


Sun, 19 Jul 2026 15:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEAL_WRITE When SEAL_EXEC is added, SEAL_WRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means one can use SEAL_EXEC to apply SEAL_WRITE while having writeable mappings. This breaks the contract that SEAL_WRITE provides and can be used by an attacker to pass a memfd that appears to be write sealed but can still be modified arbitrarily. Fix this by adding the implied seals before the call for mapping_deny_writable() is done.
Title memfd: deny writeable mappings when implying SEAL_WRITE
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-05T12:37:37.398Z

Reserved: 2026-07-19T07:54:57.023Z

Link: CVE-2026-63952

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity : Important

Publid Date: 2026-07-19T00:00:00Z

Links: CVE-2026-63952 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T06:45:03Z

Weaknesses
  • CWE-266

    Incorrect Privilege Assignment