Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-63952memfd: deny writeable mappings when implying SEAL_WRITE

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63952, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.4CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
NVDNVD · Analyzed3.1High8.4CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (22 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.4.

Affected products

  • Linux · Linux

    • affected c4f75bc8bd6b3d62665e1f5400c419540edb5601 – < b3f4f82d1315f1439059a83d1c22c51a5b43d99e
    • affected c4f75bc8bd6b3d62665e1f5400c419540edb5601 – < 3be2a24f7f72ad7321ed6ad1715b956a4527bcf4
    • affected c4f75bc8bd6b3d62665e1f5400c419540edb5601 – < 0995d1f79aed8ccbf62056189dd53fd19726ea08
    • affected c4f75bc8bd6b3d62665e1f5400c419540edb5601 – < 555702282d4536a865dfffb1cd4f6028f196e7e8
    • affected c4f75bc8bd6b3d62665e1f5400c419540edb5601 – < 3b041514cb6eae45869b020f743c14d983363222
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.93 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.0.12 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63952 badge
[![CVE-2026-63952](https://cveledger.app/badge/CVE-2026-63952.svg)](https://cveledger.app/cve/CVE-2026-63952)

Record last updated .