Live › vulnerability › CVE-2026-99222
The Linux kernel's keyctl read path checks a key type's read method outside the lock that protects it, so a key can be read while the RxRPC module is being unloaded. The sources describe this as reading freed module memory, which can crash the system or be abused locally.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 16:24 UTC. All times on this page are UTC.
Only systems where the RxRPC key type is present and AF_RXRPC can be unloaded are described as relevant; the sources do not say more. Systems that do not load the rxrpc module are likely not affected, but the sources do not confirm this.
No product ranges from the sources yet.
uname -r and compare against the fixed kernel versions in the upstream stable tree (not stated in the sources)lsmod | grep rxrpcUnknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
keys: Protect the read method check against type removal
keyctl_read_key() checks key->type->read without holding key->sem. A reference keeps the key alive, but does not pin the module containing its type. A surviving RxRPC key can therefore be read while AF_RXRPC is being unloaded:
KEYCTL_READ task Module unload and key GC
lookup_user_key() permission / possession checks load key->type af_rxrpc_exit() unregister_key_type() GC: down_write(key->sem) GC: retype to key_type_dead GC: up_write(key->sem) unregister_key_type() returns free_module() read saved type's read member
The final access can read freed module storage. The read invocation in __keyctl_read_key() is already protected by key->sem, but the earlier method check is outside that critical section.
Move the method check into __keyctl_read_key(), after key_validate() and under its existing read hold on key->sem. The check and invocation then use the same protected type for length queries and every read retry. The GC cannot retype the key until the semaphore is released, and type unregistration waits for that GC pass before the module can be freed.
Return -EOPNOTSUPP when validation succeeds and the type has no read method. A temporary buffer may now be allocated before this result; allocation and copying to userspace remain outside the semaphore.
This page as .md · .json · in your agent: get_signal("CVE-2026-99222")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.