CVE-2026-99225 Uso después de liberar en la búsqueda de llaveros de proceso del kernel de Linux
En el kernel de Linux, search_process_keyrings_rcu() valida la clave de autorización pero luego lee payload.data[0] y rka-cred sin que la validación impida que request_key_auth_revoke() limpie el payload. Un helper de request-key puede provocar el uso de credenciales guardadas ya invalidadas.
CVSS 3.1 · PRELIMINAR
- Probabilidad de explotación · EPSS del 09/110,2 % · percentil 7
- Explotada activamenteNo confirmada
- Exploit públicoNo conocido
Afectados
Linux
desde e59428f721ee096d8a020504ea908a6f0d952735 hasta antes de 14fb6fad526b35a7ebd121f1dd313abe652e0aa6desde e59428f721ee096d8a020504ea908a6f0d952735 hasta antes de 458cf9715af6aff3ac8d2ec60bd59e9d6236fd0fdesde e59428f721ee096d8a020504ea908a6f0d952735 hasta antes de 7d3d2fffe933e538472ccafe5bbc7109488b9ce3desde e59428f721ee096d8a020504ea908a6f0d952735 hasta antes de 26949c2e4c461e9e620e935bc22717f36a40b615desde e59428f721ee096d8a020504ea908a6f0d952735 hasta antes de 984a178d54515779a1bee100b92a6cee8777c830desde e59428f721ee096d8a020504ea908a6f0d952735 hasta antes de b86db7993051d05810601654e886a1e78e1fa495desde e59428f721ee096d8a020504ea908a6f0d952735 hasta antes de b4dfda438fee3c6faa15d9b421c373de6a0e476fdesde e59428f721ee096d8a020504ea908a6f0d952735 hasta antes de 49f4e768540d25d8852ef750313afda6a4774871desde e59428f721ee096d8a020504ea908a6f0d952735 hasta antes de 0a0ec45bf577a9b4d4960567f20d3877ef480de9
Linux
5.3
Qué hacer
- Verificá si usás Linux y en qué versión.
- Actualizá a la versión corregida que indique el fabricante en su aviso o aplicá su mitigación.
- Revisá registros y accesos de los sistemas expuestos para descartar un uso previo.
Calculadora CVSS
Esta vulnerabilidad todavía no tiene vector CVSS publicado.
Descripción original
In the Linux kernel, the following vulnerability has been resolved:
keys: Check the authorization payload in process keyring searches
An authorization payload and its saved credentials must remain valid
while search_process_keyrings_rcu() searches the requestor's keyrings.
The function validates the authorization key, then separately loads
payload.data[0] and unconditionally reads rka->cred. Validation does
not prevent request_key_auth_revoke() from clearing the payload.
A request-key helper can assume authority and fork a descendant that
inherits the authorization key. If the descendant misses in its own
keyrings, it falls back to the saved requestor credentials. Successful
target instantiation invalidates the authorization key without clearing
the payload. After the helper exits, UMH_WAIT_PROC returns to the
requester, which calls complete_request_key() and revokes that key.
With the descendant paused after validation, the paths can interleave
as follows:
1. The descendant enters search_process_keyrings_rcu() under RCU and
key_validate() succeeds.
2. The helper instantiates the target, invalidates the authorization
key, and exits.
3. The requester resumes from UMH_WAIT_PROC, calls
complete_request_key(), and revokes the authorization key.
request_key_auth_revoke() sets its payload pointer to NULL.
4. The descendant loads NULL and dereferences rka->cred.
This NULL dereference can oops the kernel. RCU delays payload disposal
but does not prevent the pointer from being cleared.
Load the payload with dereference_key_rcu() and require a non-NULL
result before validating the authorization key and searching its saved
credentials. A non-NULL payload and its credentials remain alive for
the caller's RCU read-side section; a cleared payload skips the fallback
search and follows the existing error selection.
KASAN report as below:
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
RIP: 0010:search_process_keyrings_rcu+0x32b/0x790
Referencias (9)
- git.kernel.org/stable/c/14fb6fad526b35a7ebd121f1dd313abe652e0aa6
- git.kernel.org/stable/c/458cf9715af6aff3ac8d2ec60bd59e9d6236fd0f
- git.kernel.org/stable/c/7d3d2fffe933e538472ccafe5bbc7109488b9ce3
- git.kernel.org/stable/c/26949c2e4c461e9e620e935bc22717f36a40b615
- git.kernel.org/stable/c/984a178d54515779a1bee100b92a6cee8777c830
- git.kernel.org/stable/c/b86db7993051d05810601654e886a1e78e1fa495
- git.kernel.org/stable/c/b4dfda438fee3c6faa15d9b421c373de6a0e476f
- git.kernel.org/stable/c/49f4e768540d25d8852ef750313afda6a4774871
- git.kernel.org/stable/c/0a0ec45bf577a9b4d4960567f20d3877ef480de9
Resumen traducido automáticamente de la descripción original. Fuente: Nureq Monitor. Cómo funciona.