# CVE-2026-99224: keys: Protect the type name while describing a key

CVE-2026-99224 is fixed in linux on 1 platform, first by DEBIAN-CVE-2026-99224, released November 3, 2026. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2026-99224
- Priority: High
- CVSS: 7.0 (Moderate)
- EPSS: 0.0012
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Nov 2, 2026
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-99224

## 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

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 13.5 (trixie) | 6.12.115-1 | [DEBIAN-CVE-2026-99224](https://patchblox.com/security/data/fix/linux/debian-cve-2026-99224.md) | Nov 3, 2026 |
| Linux | linux Debian 14 | 7.2.14-1 | [DEBIAN-CVE-2026-99224](https://patchblox.com/security/data/fix/linux/debian-cve-2026-99224.md) | Nov 3, 2026 |

---

Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.