CVE-2026-104039
Description
A flaw was found in SSSD. A local user can cause a denial of service (DoS) by disrupting system authentication services. When handling Generic Security Services Application Programming Interface (GSSAPI) authentication in the Pluggable Authentication Module (PAM) responder, cached connection state is freed upon completion without clearing the reference pointer. An attacker can exploit this by sending an additional request over the same connection, causing the service to access invalid memory and unexpectedly terminate.
Statement
This vulnerability is rated as Moderate because exploitation requires local access, specific non-default configuration, and an established session, resulting solely in a denial of service. The flaw is only reachable when SSSD's PAM responder has GSSAPI authentication explicitly configured and enabled for specific services. Furthermore, triggering the condition requires an authenticated local user to complete an initial GSSAPI context handshake and subsequently submit an additional request over the same connection. Because exploitation crashes the PAM responder process without compromising system confidentiality or integrity, the overall risk is reduced.
Mitigation
A workaround is available for this issue. PAM GSSAPI authentication can be disabled in the SSSD configuration: edit /etc/sssd/sssd.conf, and in the [pam] section remove or comment out the pam_gssapi_services option (or set it to an empty value), so that no service is permitted to use GSSAPI authentication through the PAM responder. Then restart the SSSD service (systemctl restart sssd) to apply the change. Note that disabling PAM GSSAPI authentication prevents clients from authenticating to the affected PAM services using Kerberos tickets, requiring them to use alternative authentication methods such as passwords. Restarting the SSSD service also briefly disrupts ongoing authentication requests. Restarting the PAM responder can restore service after a crash, but it does not remove the underlying flaw.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.7 | 5.5 | 4.7 |
| Attack Vector | Local | Local | Local |
| Attack Complexity | High | Low | High |
| Privileges Required | Low | Low | Low |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | None | None | None |
| Integrity Impact | None | None | None |
| Availability Impact | High | High | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Acknowledgements
This issue was discovered by Found by AISLE in partnership with Red Hat.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
