In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEAL_WRITE When SEAL_EXEC is added,… (CVE-2026-63952)
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.
AI Analysis
Technical Summary
The Linux kernel memfd feature uses seals to restrict modifications. When SEAL_EXEC is added, SEAL_WRITE is implicitly applied to enforce a write-protection policy (W^X). However, the original implementation applied the implied SEAL_WRITE after the check that denies writable mappings, allowing writable mappings to exist despite the seal. This flaw permits an attacker to present a memfd as write-sealed while retaining writable access, violating the seal's contract. The fix involves applying the implied seals before the writable mapping denial check, restoring the intended protection.
Potential Impact
An attacker could exploit this vulnerability to modify memfd contents that are supposed to be write-protected by SEAL_WRITE, potentially undermining security mechanisms relying on memfd immutability guarantees. This could affect processes or components that depend on memfd seals to enforce memory protection policies.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since this is a kernel vulnerability, monitor official Linux kernel advisories for patches addressing CVE-2026-63952 and apply updates promptly once available.
In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEAL_WRITE When SEAL_EXEC is added,… (CVE-2026-63952)
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.
CVSS v3.1
Score 8.4high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel memfd feature uses seals to restrict modifications. When SEAL_EXEC is added, SEAL_WRITE is implicitly applied to enforce a write-protection policy (W^X). However, the original implementation applied the implied SEAL_WRITE after the check that denies writable mappings, allowing writable mappings to exist despite the seal. This flaw permits an attacker to present a memfd as write-sealed while retaining writable access, violating the seal's contract. The fix involves applying the implied seals before the writable mapping denial check, restoring the intended protection.
Potential Impact
An attacker could exploit this vulnerability to modify memfd contents that are supposed to be write-protected by SEAL_WRITE, potentially undermining security mechanisms relying on memfd immutability guarantees. This could affect processes or components that depend on memfd seals to enforce memory protection policies.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since this is a kernel vulnerability, monitor official Linux kernel advisories for patches addressing CVE-2026-63952 and apply updates promptly once available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6pc4-h32v-99rg
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63952"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- 3.1
Threat ID: 6a5d27aa2a4a8d598912ebe8
Added to database: 07/19/2026, 19:38:18 UTC
Last enriched: 07/19/2026, 20:06:01 UTC
Last updated: 09/02/2026, 22:52:13 UTC
Views: 62
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.