Medium [CVE-2026-104037] Sssd: sssd: denial of service via packet length underflow in autofs responder
This medium-severity Red Hat Linux advisory covers CVE-2026-104037 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in SSSD. A local attacker can exploit this issue by sending a specially crafted request with an invalid packet length to the autofs responder UNIX socket.
This causes an integer underflow and an out-of-bounds memory read, which can crash the responder process and result in a denial of service (DoS).
This vulnerability is rated as Moderate because exploitation is limited to a local denial of service against the SSSD autofs responder daemon, without enabling privilege escalation or data confidentiality/integrity loss. The autofs responder is only exposed if enabled in the SSSD configuration and accessible through its local UNIX socket.
Systems where SSSD does not manage automount maps or where the autofs responder is inactive are unaffected by this issue. Red Hat severity: Moderate — CVSS 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
Weakness: CWE-125. Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat OpenShift Container Platform 4.
Will not fix / out of support: Red Hat Enterprise Linux 6. Red Hat does not currently list a fixing RHSA for this CVE.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation checklist
- If automount map integration via SSSD is not required, disable the autofs responder service: 1. Stop and mask the socket-activated service: ```bash systemctl stop sssd-autofs.socket sssd-autofs.service systemctl mask sssd-autofs.socket ``` 2. If `autofs` is explicitly defined in `/etc/sssd/sssd.conf`, remove `autofs` from the `services` directive under the `[sssd]` section and restart the SSSD service: ```bash systemctl restart sssd ``` Caveats: Disabling the responder prevents SSSD from resolving automount maps. Warning: Modifying these configurations and restarting SSSD will disrupt active automount operations and may temporarily impact identity lookups during the service restart.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.