NULL Pointer Dereference Affecting openshift/ose-rhel-coreos-9 package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL7-OPENSHIFTOSERHELCOREOS9-22369623
- published8 Nov 2026
- disclosed2 Nov 2026
Introduced: 2 Nov 2026
NewCVE-2026-99225 (opens in a new tab)How to fix?
There is no fixed version for RHEL:7 openshift/ose-rhel-coreos-9.
NVD Description
Note: Versions mentioned in the description apply only to the upstream openshift/ose-rhel-coreos-9 package and not the openshift/ose-rhel-coreos-9 package as distributed by RHEL.
See How to fix? for RHEL:7 relevant fixed versions and status.
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:
- The descendant enters search_process_keyrings_rcu() under RCU and key_validate() succeeds.
- The helper instantiates the target, invalidates the authorization key, and exits.
- 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.
- 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
References
- https://access.redhat.com/security/cve/CVE-2026-99225
- https://git.kernel.org/stable/c/14fb6fad526b35a7ebd121f1dd313abe652e0aa6
- https://git.kernel.org/stable/c/26949c2e4c461e9e620e935bc22717f36a40b615
- https://git.kernel.org/stable/c/458cf9715af6aff3ac8d2ec60bd59e9d6236fd0f
- https://git.kernel.org/stable/c/49f4e768540d25d8852ef750313afda6a4774871
- https://git.kernel.org/stable/c/7d3d2fffe933e538472ccafe5bbc7109488b9ce3
- https://git.kernel.org/stable/c/984a178d54515779a1bee100b92a6cee8777c830
- https://git.kernel.org/stable/c/b4dfda438fee3c6faa15d9b421c373de6a0e476f
- https://git.kernel.org/stable/c/b86db7993051d05810601654e886a1e78e1fa495
- https://git.kernel.org/stable/c/0a0ec45bf577a9b4d4960567f20d3877ef480de9