Skip to main content
← Vulnerabilities

keys: Protect the type name while describing a key

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

7.0HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. AF_RXRPC is built as a module (AF_RXRPC=m) A task passes View permission on the key before its type is retired while a privileged module is unloaded

Published
Last modified
Published
Not listed in CISA KEV
37/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post

Summary

The Linux kernel's key management subsystem (the keyctl KEYCTL_DESCRIBE path) is affected when the AF_RXRPC networking module is built as a loadable module. A race with unloading that module can cause the kernel to read a key type name from freed module memory, leading to a kernel crash (oops) due to a page fault.

Read the original description

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

What to do

  • Check whether your setup matches what the bug needs.

    AF_RXRPC is built as a module (AF_RXRPC=m) A task passes View permission on the key before its type is retired while a privileged module is unloaded
  • Workaround: The checked facts list no fix and no workaround. The only condition they name is AF_RXRPC built as a module, so they give no other way to limit exposure.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

  • Linux Linux

    Version range not reported

  • Linux Linux

    3.18

Evidence 8

  1. Link
  2. Link
  3. Link
  4. Link
  5. Link
Show all 8 sourcesShow fewer sources
  1. Link
  2. Link
  3. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-99224

What does this mean?

A task that holds View permission on a key can trigger a read of freed module memory when a privileged module is unloaded while the key's type is being retired. That read can cause a kernel page fault (oops) during key description.Source: git.kernel.org

Am I affected, and how do I check?

The checked facts list only the Linux kernel with AF_RXRPC built as a module (AF_RXRPC=m) as the affected setup, and they name no affected version range. To check a kernel build, look at whether AF_RXRPC is set to m in its build configuration.Source: git.kernel.org

What should I do about it?

The checked facts name no fixed version, so no upgrade target can be given. Check the kernel's own security sources for a patched release.Source: git.kernel.org

Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What if there's no patch?

The checked facts list no fix and no workaround. The only condition they name is AF_RXRPC built as a module, so they give no other way to limit exposure.Source: git.kernel.org