P11-kit: null dereference via c_derivekey with specific null parameters
Published Mar 26, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
P11-kit: null dereference via c_derivekey with specific null parameters
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
A flaw was found in p11-kit. A remote attacker could exploit this vulnerability by calling the C_DeriveKey function on a remote token with specific IBM kyber or IBM btc derive mechanism parameters set to NULL. This could lead to the RPC-client attempting to return an uninitialized value, potentially resulting in a NULL dereference or undefined behavior. This issue may cause an application level denial of service or other unpredictable system states.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
Record history
Published Mar 26, 2026 · Last refreshed Nov 3, 2026