glibc - Debian Package Tracker

general

source: glibc (main)
version: 2.42-10
maintainer: GNU Libc Maintainers (archive) (DMD)
uploaders: Samuel Thibault [DMD] – Aurelien Jarno [DMD] – Clint Adams [DMD]
arch: all any
std-ver: 4.6.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2.31-13+deb11u11
o-o-sec: 2.31-13+deb11u13
o-o-upd: 2.31-13+deb11u5
o-o-p-u: 2.31-13+deb11u11
oldstable: 2.36-9+deb12u13
old-sec: 2.36-9+deb12u7
stable: 2.41-12
testing: 2.42-10
unstable: 2.42-10

versioned links

2.31-13+deb11u5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.31-13+deb11u11: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.31-13+deb11u13: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.36-9+deb12u7: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.36-9+deb12u13: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.41-12: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.42-10: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

glibc-doc (8 bugs: 0, 1, 7, 0)
glibc-source (1 bugs: 0, 0, 1, 0)
libc-bin (23 bugs: 0, 10, 13, 0)
libc-dev-bin (1 bugs: 0, 1, 0, 0)
libc-devtools (1 bugs: 0, 1, 0, 0)
libc-gconv-modules-extra
libc-l10n
libc0.3
libc0.3-dbg
libc0.3-dev
libc0.3-udeb
libc6 (217 bugs: 0, 154, 63, 0)
libc6-amd64 (1 bugs: 0, 1, 0, 0)
libc6-dbg (1 bugs: 0, 0, 1, 0)
libc6-dev (31 bugs: 0, 17, 14, 0)
libc6-dev-amd64
libc6-dev-i386
libc6-dev-mips32
libc6-dev-mips64
libc6-dev-mipsn32
libc6-dev-powerpc
libc6-dev-ppc64
libc6-dev-s390
libc6-dev-sparc
libc6-dev-sparc64
libc6-dev-x32
libc6-i386 (2 bugs: 0, 1, 1, 0)
libc6-mips32
libc6-mips64
libc6-mipsn32
libc6-powerpc
libc6-ppc64
libc6-s390
libc6-sparc
libc6-sparc64
libc6-udeb
libc6-x32 (1 bugs: 0, 1, 0, 0)
libc6.1
libc6.1-dbg
libc6.1-dev
libc6.1-udeb
locales (49 bugs: 0, 31, 18, 0)
locales-all (3 bugs: 0, 2, 1, 0)
nscd (28 bugs: 0, 25, 3, 0)

action needed

1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:

CVE-2025-15281: Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.

Created: 2026-01-20 Last update: 2026-01-23 20:33

1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:

CVE-2025-15281: Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.

Created: 2026-01-20 Last update: 2026-01-23 20:33

6 security issues in bullseye high

There are 6 open security issues in bullseye.

3 important issues:

CVE-2026-0861: Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption. Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc. Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.
CVE-2026-0915: Calling getnetbyaddr or getnetbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend for networks and queries for a zero-valued network in the GNU C Library version 2.0 to version 2.42 can leak stack contents to the configured DNS resolver.
CVE-2025-15281: Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.

1 issue postponed or untriaged:

CVE-2025-8058: (postponed; to be fixed through a stable update) The regcomp function in the GNU C library version from 2.4 to 2.41 is subject to a double free if some previous allocation fails. It can be accomplished either by a malloc failure or by using an interposed malloc that injects random malloc failures. The double free can allow buffer manipulation depending of how the regex is constructed. This issue affects all architectures and ABIs supported by the GNU C library.

2 ignored issues:

CVE-2023-4806: A flaw has been identified in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the _nss_*_gethostbyname2_r and _nss_*_getcanonname_r hooks without implementing the _nss_*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags.
CVE-2023-4813: A flaw has been identified in glibc. In an uncommon situation, the gaih_inet function may use memory that has been freed, resulting in an application crash. This issue is only exploitable when the getaddrinfo function is called and the hosts database in /etc/nsswitch.conf is configured with SUCCESS=continue or SUCCESS=merge.

Created: 2026-01-15 Last update: 2026-01-23 20:33

lintian reports 10 errors and 36 warnings high

Lintian reports 10 errors and 36 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2026-01-18 Last update: 2026-01-21 07:30

7 security issues in buster high

There are 7 open security issues in buster.

4 important issues:

CVE-2024-33599: nscd: Stack-based buffer overflow in netgroup cache If the Name Service Cache Daemon's (nscd) fixed size cache is exhausted by client requests then a subsequent client request for netgroup data may result in a stack-based buffer overflow. This flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary.
CVE-2024-33600: nscd: Null pointer crashes after notfound response If the Name Service Cache Daemon's (nscd) cache fails to add a not-found netgroup response to the cache, the client request can result in a null pointer dereference. This flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary.
CVE-2024-33601: nscd: netgroup cache may terminate daemon on memory allocation failure The Name Service Cache Daemon's (nscd) netgroup cache uses xmalloc or xrealloc and these functions may terminate the process due to a memory allocation failure resulting in a denial of service to the clients. The flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary.
CVE-2024-33602: nscd: netgroup cache assumes NSS callback uses in-buffer strings The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. The flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary.

2 issues postponed or untriaged:

CVE-2023-4806: (needs triaging) A flaw was found in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the _nss_*_gethostbyname2_r and _nss_*_getcanonname_r hooks without implementing the _nss_*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags.
CVE-2023-4813: (needs triaging) A flaw was found in glibc. In an uncommon situation, the gaih_inet function may use memory that has been freed, resulting in an application crash. This issue is only exploitable when the getaddrinfo function is called and the hosts database in /etc/nsswitch.conf is configured with SUCCESS=continue or SUCCESS=merge.

1 ignored issue:

CVE-2020-1751: An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC. Specifically, the backtrace function did not properly check the array bounds when storing the frame address, resulting in a denial of service or potential code execution. The highest threat from this vulnerability is to system availability.

Created: 2024-04-17 Last update: 2024-06-29 13:15

Depends on packages which need a new maintainer normal

The packages that glibc depends on which need a new maintainer are:

systemtap (#1114760)
- Build-Depends: systemtap-sdt-dev

Created: 2026-01-04 Last update: 2026-01-25 08:30

35 bugs tagged patch in the BTS normal

The BTS contains patches fixing 35 bugs (41 if counting merged bugs), consider including or untagging them.

Created: 2025-01-06 Last update: 2026-01-25 06:00

version in VCS is newer than in repository, is it time to upload? normal

vcswatch reports that this package seems to have a new changelog entry (version 2.42-11, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:

commit d1e0d17d1060b8fcf52104dd6522c59de92ed659
Author: Aurelien Jarno <aurelien@aurel32.net>
Date:   Sat Jan 24 13:29:02 2026 +0100

    debian/patches/git-updates.diff: update from upstream stable branch:
    
    * debian/patches/git-updates.diff: update from upstream stable branch:
      - Fix bug in wordexp, which could return uninitialized memory when using
        WRDE_REUSE together with WRDE_APPEND (CVE-2025-15281).  Closes: #1126266.
      - Switch currency symbol for the bg_BG locale to euro.

commit c79af7a16ed823ba05745b4c2aa0c22637750051
Author: Aurelien Jarno <aurelien@aurel32.net>
Date:   Sat Jan 24 13:14:08 2026 +0100

    Retroactively add bug number for CVE-2026-0915

commit 33d0c3c3b932f4ed08eec7d99588464b63ffe053
Author: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date:   Thu Jan 22 01:38:21 2026 +0000

    hurd: Work around missing execstack on libc.so
    
    It seems that binutils ≥ 2.45.50.202601 mis-computes that we need execstack
    on libc.so.  Work around it for now.
    
    * debian/patches/hurd-i386/local-execstack.diff

Created: 2026-01-22 Last update: 2026-01-24 14:31

4 open merge requests in Salsa normal

There are 4 open merge requests for this package on Salsa. You should consider reviewing and/or merging these merge requests.

Created: 2025-09-21 Last update: 2026-01-09 22:32

3 low-priority security issues in trixie low

There are 3 open security issues in trixie.

3 issues left for the package maintainer to handle:

CVE-2026-0861: (needs triaging) Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption. Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc. Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.
CVE-2026-0915: (needs triaging) Calling getnetbyaddr or getnetbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend for networks and queries for a zero-valued network in the GNU C Library version 2.0 to version 2.42 can leak stack contents to the configured DNS resolver.
CVE-2025-15281: (needs triaging) Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.

You can find information about how to handle these issues in the security team's documentation.

Created: 2026-01-15 Last update: 2026-01-23 20:33

3 low-priority security issues in bookworm low

There are 3 open security issues in bookworm.

3 issues left for the package maintainer to handle:

CVE-2026-0861: (needs triaging) Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption. Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc. Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.
CVE-2026-0915: (needs triaging) Calling getnetbyaddr or getnetbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend for networks and queries for a zero-valued network in the GNU C Library version 2.0 to version 2.42 can leak stack contents to the configured DNS resolver.
CVE-2025-15281: (needs triaging) Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.

You can find information about how to handle these issues in the security team's documentation.

Created: 2026-01-15 Last update: 2026-01-23 20:33

debian/patches: 77 patches to forward upstream low

Among the 77 debian patches available in version 2.42-10 of the package, we noticed the following issues:

77 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2026-01-20 11:00

Issues found with some translations low

Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.

Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.

Created: 2020-02-26 Last update: 2025-12-07 14:00

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.3 instead of 4.6.2).

Created: 2024-04-07 Last update: 2026-01-19 22:19

testing migrations

This package will soon be part of the s390-31-bit-rm transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.

news

[rss feed]

[2026-01-22] glibc 2.42-10 MIGRATED to testing (Debian testing watch)
[2026-01-20] glibc 2.42-9 MIGRATED to testing (Debian testing watch)
[2026-01-19] Accepted glibc 2.42-10 (source) into unstable (Aurelien Jarno)
[2026-01-18] Accepted glibc 2.42-9 (source) into unstable (Aurelien Jarno)
[2026-01-16] Accepted glibc 2.42-8 (source) into unstable (Aurelien Jarno)
[2026-01-12] glibc 2.42-7 MIGRATED to testing (Debian testing watch)
[2026-01-04] Accepted glibc 2.42-7 (source) into unstable (Aurelien Jarno)
[2026-01-01] Accepted glibc 2.41-12+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Aurelien Jarno)
[2025-12-20] glibc 2.42-6 MIGRATED to testing (Debian testing watch)
[2025-12-12] Accepted glibc 2.42-6 (source) into unstable (Aurelien Jarno)
[2025-12-12] glibc 2.42-5 MIGRATED to testing (Debian testing watch)
[2025-12-06] Accepted glibc 2.42-5 (source) into unstable (Aurelien Jarno)
[2025-12-03] Accepted glibc 2.42-4 (source) into unstable (Aurelien Jarno)
[2025-11-29] Accepted glibc 2.42-3 (source) into experimental (Aurelien Jarno)
[2025-09-02] Accepted glibc 2.42-2 (source) into experimental (Aurelien Jarno)
[2025-08-27] Accepted glibc 2.36-9+deb12u13 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Aurelien Jarno)
[2025-08-12] Accepted glibc 2.42-1 (source all amd64) into experimental (Debian FTP Masters) (signed by: Aurelien Jarno)
[2025-08-08] glibc 2.41-12 MIGRATED to testing (Debian testing watch)
[2025-08-07] glibc 2.41-12 MIGRATED to testing (Debian testing watch)
[2025-08-05] Accepted glibc 2.41-12 (source) into unstable (Aurelien Jarno)
[2025-07-30] glibc 2.41-11 MIGRATED to testing (Debian testing watch)
[2025-07-26] Accepted glibc 2.41-11 (source) into unstable (Aurelien Jarno)
[2025-07-22] glibc 2.41-10 MIGRATED to testing (Debian testing watch)
[2025-07-17] Accepted glibc 2.41-10 (source) into unstable (Aurelien Jarno)
[2025-06-24] glibc 2.41-9 MIGRATED to testing (Debian testing watch)
[2025-06-18] Accepted glibc 2.41-9 (source) into unstable (Aurelien Jarno)
[2025-06-03] Accepted glibc 2.36-9+deb12u12 (source) into proposed-updates (Debian FTP Masters) (signed by: Aurelien Jarno)
[2025-05-31] Accepted glibc 2.36-9+deb12u11 (source) into proposed-updates (Debian FTP Masters) (signed by: Aurelien Jarno)
[2025-05-27] Accepted glibc 2.31-13+deb11u13 (source) into oldstable-security (Sean Whitton)
[2025-05-23] glibc 2.41-8 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 415 438
RC: 0
I&N: 270 287
M&W: 145 151
F&P: 0
patch: 35 41

links

homepage
lintian (10, 36)
buildd: logs, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
l10n (84, 97)
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.42-2ubuntu4
447 bugs (8 patches)
patches for 2.42-2ubuntu4