Opened 3 weeks ago

Closed 6 days ago

#6023 closed enhancement (fixed)

Fix various security vulnerabilities in glibc-2.44

Reported by: Xi Ruoyao Owned by: SecurityAdvisory
Priority: high Milestone: 13.2
Component: Errata Version: git
Severity: normal Keywords:
Cc:

Description

There are some security vulnerabilities fixed after glibc-2.44:

advisories/GLIBC-SA-2026-0015:CVE-Id: CVE-2026-18374
advisories/GLIBC-SA-2026-0017:CVE-Id: CVE-2026-19499
advisories/GLIBC-SA-2026-0018:CVE-Id: CVE-2026-19542
advisories/GLIBC-SA-2026-0019:CVE-Id: CVE-2026-77117
advisories/GLIBC-SA-2026-0020:CVE-Id: CVE-2026-80489
advisories/GLIBC-SA-2026-0021:CVE-Id: CVE-2026-8674

GLIBC-SA-2026-0014 and earlier are already fixed in 2.44. GLIBC-SA-2026-0016 is for nscd that we've disabled already.

I have doubts about some of them (at least, CVE-2026-18374 seems just a normal bug with almost no security implication to me) but let's fix them anyway. As the current upstream fixes patch is a bulk one containing everything (at that moment) on the glibc-2.44 maintenance branch, I'll just export a new patch containing everything on the branch as at now as well.

Change History (8)

comment:1 by Xi Ruoyao, 3 weeks ago

Owner: changed from lfs-book to Xi Ruoyao
Status: new → assigned

comment:2 by Xi Ruoyao, 3 weeks ago

Fixed at r13.1-7-g4e488b925. I don't know if I'll have the mood to write advisory.

comment:3 by Xi Ruoyao, 3 weeks ago

Component: Book → Errata
Owner: changed from Xi Ruoyao to SecurityAdvisory
Status: assigned → new

in reply to:  2 comment:4 by Bruce Dubbs, 3 weeks ago

Replying to Xi Ruoyao:

Fixed at r13.1-7-g4e488b925. I don't know if I'll have the mood to write advisory.

I'll do it.

comment:5 by Joe Locash, 2 weeks ago

GLIBC-SA-2026-0022 and GLIBC-SA-2026-0023 were announced today:

Message-ID: <a7a19d53-0124-482f-a7bb-7dfb42c8ae48@redhat.com>
Date: Tue, 22 Sep 2026 12:52:12 -0400
From: Carlos O'Donell <carlos@...hat.com>
To: oss-security@...ts.openwall.com
Subject: The GNU C Library security advisories update for 2026-09-22

The following security advisories have been published:

GLIBC-SA-2026-0022:
===================
AT_SECURE programs may load attacker-controlled code via $ORIGIN

A time-of-check to time-of-use (TOCTOU) race condition in the dynamic
loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44
allows a local attacker to escalate privileges. When expanding $ORIGIN
in DT_RPATH for setuid/setgid (AT_SECURE) programs, glibc validates the
lexically normalized search path against the trusted directories but
then opens the raw, un-normalized path. On systems where the Linux
fs.protected_hardlinks sysctl is disabled, a local attacker who
hard-links such a program into an attacker-controlled directory and wins
a race to replace an intermediate path component with a symbolic link
can direct the loader outside the trusted directory, causing it to load
an attacker-controlled shared object and execute arbitrary code with the
elevated privileges of the program.

Exploitation requires an installed setuid or setgid binary whose DT_RPATH
uses $ORIGIN followed by ".." traversal that normalizes into a trusted
directory, and the ability to hard-link that binary and win the race by
swapping a path component for a symbolic link. Major Linux-based OS
distributions ship with fs.protected_hardlinks enabled by default and
mitigate the vulnerability.

CVE-Id: CVE-2026-86805
Public-Date: 2026-07-06
Vulnerable-Commit: 47c3cd7a74e8c089d60d603afce6d9cf661178d6 (2.13-113)
Fix-Commit: ed0c137b97eb940b4b64981e84ed806d3276edd9 (2.45)
Reported-by: Jann Horn <jannh@...gle.com>
CVSS: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L - 6.3

GLIBC-SA-2026-0023:
===================
AT_SECURE program buffer overflow via $ORIGIN processing

A stack-based buffer overflow in the dynamic loader (ld.so) of the GNU C
Library (glibc) versions 2.14 through 2.44 allows a local attacker to
crash or corrupt the memory of setuid/setgid (AT_SECURE) programs.

When such a program's DT_RPATH or DT_RUNPATH begins with $ORIGIN and is
followed by NUL or '/' the loader both reads past the end of the path
buffer and writes past the end of a stack-allocated internal buffer.
The corrupted loader stack can lead to a loader crash (denial of
service) and limited disclosure of process memory.

CVE Id: CVE-2026-95818
Public-Date: 2026-08-14
Vulnerable-Commit: 47c3cd7a74e8c089d60d603afce6d9cf661178d6 (2.13-113)
Fix-Commit: ed0c137b97eb940b4b64981e84ed806d3276edd9 (2.45)
Reported-by: AISLE in partnership with Red Hat
CVSS: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N - 3.6

comment:6 by Xi Ruoyao, 2 weeks ago

See #6028 for the new ones. I don't think we have an exploit on (B)LFS.

comment:7 by Bruce Dubbs, 8 days ago

Fixed at a part of commit 9bb7b28d5 where glibc-2.44-upstream_fixes-3.patch was added.

comment:8 by Bruce Dubbs, 6 days ago

Resolution: → fixed
Status: new → closed

Advisory sa-13.1-043 has been issued.

Note: See TracTickets for help on using tickets.