VulnerabilityPublished 24 Sep 2026Updated 30 Oct 2026

CVE-2026-93243: Linux kernel · mm/secretmem: properly account locked pages

Source GCVE Database

Compare

Authoritative record:CVE-2026-93243· High

Not known to be exploited · fixed in a41c95ac90f285cbe473b9606428b14518896ea4 : patch Linux kernel soon.

Data as of 30 Oct 2026, 18:03 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in a41c95ac90f285cbe473b9606428b14518896ea4, 853043cb129473ff2fa0090602be944d96b9d5c9, 97d34aa65c29cca85e3e9050f4c936389b38a054 +3

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-9q86-wxfp-682m

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 1507f51255c9ff07d75909a84e7c0d7f3c4b2f49, < a41c95ac90f285cbe473b9606428b14518896ea4	Fixed in a41c95ac90f285cbe473b9606428b14518896ea4
LinuxLinux	Affected ≥ 1507f51255c9ff07d75909a84e7c0d7f3c4b2f49, < 853043cb129473ff2fa0090602be944d96b9d5c9	Fixed in 853043cb129473ff2fa0090602be944d96b9d5c9
LinuxLinux	Affected ≥ 1507f51255c9ff07d75909a84e7c0d7f3c4b2f49, < 97d34aa65c29cca85e3e9050f4c936389b38a054	Fixed in 97d34aa65c29cca85e3e9050f4c936389b38a054
LinuxLinux	Affected ≥ 1507f51255c9ff07d75909a84e7c0d7f3c4b2f49, < 51fba083e454f901947d6a335eeff671171d4714	Fixed in 51fba083e454f901947d6a335eeff671171d4714
LinuxLinux	Affected ≥ 1507f51255c9ff07d75909a84e7c0d7f3c4b2f49, < 37fd10e3d079bccf348180ff0bdac074d84ff31f	Fixed in 37fd10e3d079bccf348180ff0bdac074d84ff31f
LinuxLinux	Affected ≥ 1507f51255c9ff07d75909a84e7c0d7f3c4b2f49, < 3b4f72bdddff69819d665395376329ef21f37a06	Fixed in 3b4f72bdddff69819d665395376329ef21f37a06

AI-suggested

A fix has been implemented in the Linux kernel to properly account for locked pages in secretmem by tracking locked pages per user and removing misleading mlock() semantics. Users should apply the official kernel update that includes this fix. There is no indication that additional mitigation steps are required beyond applying the patch.

Description

CVE-2026-93243 addresses a vulnerability in the Linux kernel's secretmem subsystem where locked pages were not properly accounted for. This flaw allowed users to bypass RLIMIT_MEMLOCK limits by mapping and unmapping secretmem regions, causing these pages to remain unevictable and uncounted in process memory usage. As a result, processes could consume excessive system memory without triggering the OOM killer, potentially leading to system instability. The fix involves correctly tracking locked pages per user and removing misleading mlock() semantics for secretmem mappings.

Impact

Users could bypass memory locking limits (RLIMIT_MEMLOCK) by mapping and unmapping secretmem regions, causing unevictable memory pages to accumulate without being counted against process memory usage. This can lead to excessive memory consumption and system instability due to the OOM killer not recognizing the memory pressure. The vulnerability affects system stability and resource management but does not directly indicate privilege escalation or code execution.

References

Community reviews

Loading reviews…