Skip to content
statance
MenuClose
high · CVSS 7

CVE-2026-99224

keys: Protect the type name while describing a key

Published 2 Nov 2026 · Source updated 3 Nov 2026 · Retrieved 2026-11-05 12:07 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

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

keys: Protect the type name while describing a key

keyctl_describe_key() must keep the key type's name alive until kasprintf() has consumed it. The retained key reference keeps the key and its description alive, but does not pin the module providing its type. The name is passed to kasprintf() without holding key->sem.

kvasprintf() uses the saved name pointer in two formatting passes, with a GFP_KERNEL allocation between them. With AF_RXRPC=m, a task that passes View permission before type retirement can overlap a privileged module unload in this order:

1. KEYCTL_DESCRIBE looks up the key, saves key->type->name in the kasprintf() arguments and completes the first formatting pass. 2. While the formatter is delayed before its second pass, af_rxrpc_exit() calls unregister_key_type(), which removes the type from the registry and waits for key_gc_keytype(). 3. The collector takes key->sem for writing, retypes the retained key to key_type_dead and completes retirement. Unregistration and module exit return, allowing free_module() to release the type and name. 4. The formatter resumes its second pass and reads the saved name from released module storage, which can fault in string().

Hold key->sem for reading across kasprintf(). The collector then cannot retype the key or complete retirement until both formatting passes have finished. If retirement wins the lock first, formatting uses the core key_type_dead name instead. Release the semaphore immediately after kasprintf(), including on allocation failure, before copying to userspace.

Oops report as below:

BUG: unable to handle page fault for address: fffffbfff8054794 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page RIP: 0010:string+0x23f/0x470 Call Trace: vsnprintf+0x330/0x1110

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 to < 19c4de819e52b7f606468fbfe4fcef4e812e2777; affected: aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 to < a49e6c9a1a5b3457c946a8efb616ce13b4ca8194; affected: aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 to < 916667df7695366f23cfaf365b5840b228cc4b2e; affected: aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 to < dddd3a1ab7d12ee163477918ff6eb943361db4fe; affected: aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 to < 3c3cfd9e262afc9558c38f8cec57f09d10988546; affected: aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 to < 6b613747f7ea309ada5b8d05b55398c338f7a968; affected: aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 to < dea367df18e3a4faac393e3a4e818ee03af89b19; affected: aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 to < 0461bc8f91116aae4a020e15f4e1c1fd535ab35e; affected: aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 to < fced7238b7e80cf8aa688d5af976e4aa6e33c329See vendor advisory
LinuxLinuxaffected: 3.18; unaffected: 0 to < 3.18; unaffected: 5.10.273 to ≤ 5.10.*; unaffected: 5.15.224 to ≤ 5.15.*; unaffected: 6.1.191 to ≤ 6.1.*; unaffected: 6.6.161 to ≤ 6.6.*; unaffected: 6.12.115 to ≤ 6.12.*; unaffected: 6.18.60 to ≤ 6.18.*; unaffected: 7.2.14 to ≤ 7.2.*; unaffected: 7.3.1 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed