Answer in brief
CVE-2026-63823 records a Unknown severity vulnerability in keys: Pin request_key_auth payload in instantiate paths. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-63823 records a Unknown severity vulnerability in keys: Pin request_key_auth payload in instantiate paths. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b5f545c880a2a47947ba2118b2509644ab7a2969 <d8274181b0f28d450b42489723a5ba81042158d7 || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <4982bfabce6b33b3c9eddb4fb900fe5568b7cf91 || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <708709c65a1832a99b0eef8ae46e343ddaca3d06 || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <35ab4db86774d82389e4b9559e26ab7f68d8e395 || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <f9b68632ac93cc742f2e411021c4dbfe452ea0c2 || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <7216ce8cb12fee44e309503955bb83806b106129 || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <83c0a1cb296d955d5f4d1f0bd8a769ba8ed8c29f || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <fd15b457a86939c38aa12116adabd8ff686c5e51 | d8274181b0f28d450b42489723a5ba81042158d7, 4982bfabce6b33b3c9eddb4fb900fe5568b7cf91, 708709c65a1832a99b0eef8ae46e343ddaca3d06, 35ab4db86774d82389e4b9559e26ab7f68d8e395, f9b68632ac93cc742f2e411021c4dbfe452ea0c2, 7216ce8cb12fee44e309503955bb83806b106129, 83c0a1cb296d955d5f4d1f0bd8a769ba8ed8c29f, fd15b457a86939c38aa12116adabd8ff686c5e51 |
| Linux/Linuxgeneric | 2.6.16 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: keys: Pin request_key_auth payload in instantiate paths A: request_key() B: KEYCTL_INSTANTIATE_IOV ================ ========================= create auth key store rka in auth key wait for helper get auth key load rka from auth key copy user payload sleep on #PF helper completed detach and free rka destroy auth key wake up use rka->target_key **USE-AFTER-FREE** Give request_key_auth payloads a refcount. Take a payload reference while authkey->sem stabilizes the payload and revocation state. Hold that reference across the instantiate and reject paths. Drop the auth key owning reference from revoke and destroy. [jarkko: Replaced the first two paragraphs of text with an actual concurrency scenario.]
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b5f545c880a2a47947ba2118b2509644ab7a2969 <d8274181b0f28d450b42489723a5ba81042158d7 || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <4982bfabce6b33b3c9eddb4fb900fe5568b7cf91 || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <708709c65a1832a99b0eef8ae46e343ddaca3d06 || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <35ab4db86774d82389e4b9559e26ab7f68d8e395 || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <f9b68632ac93cc742f2e411021c4dbfe452ea0c2 || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <7216ce8cb12fee44e309503955bb83806b106129 || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <83c0a1cb296d955d5f4d1f0bd8a769ba8ed8c29f || >=b5f545c880a2a47947ba2118b2509644ab7a2969 <fd15b457a86939c38aa12116adabd8ff686c5e51 | d8274181b0f28d450b42489723a5ba81042158d7, 4982bfabce6b33b3c9eddb4fb900fe5568b7cf91, 708709c65a1832a99b0eef8ae46e343ddaca3d06, 35ab4db86774d82389e4b9559e26ab7f68d8e395, f9b68632ac93cc742f2e411021c4dbfe452ea0c2, 7216ce8cb12fee44e309503955bb83806b106129, 83c0a1cb296d955d5f4d1f0bd8a769ba8ed8c29f, fd15b457a86939c38aa12116adabd8ff686c5e51 |
| Linux/Linuxgeneric | 2.6.16 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: keys: Pin request_key_auth payload in instantiate paths A: request_key() B: KEYCTL_INSTANTIATE_IOV ================ ========================= create auth key store rka in auth key wait for helper get auth key load rka from auth key copy user payload sleep on #PF helper completed detach and free rka destroy auth key wake up use rka->target_key **USE-AFTER-FREE** Give request_key_auth payloads a refcount. Take a payload reference while authkey->sem stabilizes the payload and revocation state. Hold that reference across the instantiate and reject paths. Drop the auth key owning reference from revoke and destroy. [jarkko: Replaced the first two paragraphs of text with an actual concurrency scenario.]
Quoted source text, attributed separately from HOL analysis.