How many CVEs have patched tmp?

4 published CVEs changed tmp in debian/glibc, in 2 distinct patches totalling 88 changed lines, between 2023 and 2026.

What is the latest CVE that changed tmp?

CVE-2025-15281 (wordexp with WRDE_REUSE and WRDE_APPEND may return uninitialized memory), published 2026-01-20, changed lines 79 to 106 of sysdeps/aarch64/memrchr.S.

How does tmp compare to the rest of debian/glibc?

debian/glibc has 23 CVEs with a located fix in total; 4 of them changed tmp.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

debian/glibc

Function

2 files

tmp

Name: tmp in debian/glibc: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

Defined in 2 files

Last patched January 20, 2026

4

CVEs

That changed this function

2

Distinct patches

Backports counted once

88

Lines changed

Added plus removed

2023–2026

Years

By CVE publication date

Overview

tmp in debian/glibc was changed by 4 published CVE fixes between 2023 and 2026, in 2 distinct patches that added or removed 88 lines in total.

The name occurs in 2 files: sysdeps/aarch64/strcpy.S, sysdeps/aarch64/memrchr.S.

debian/glibc has 23 CVEs with a located fix in total, so 17% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed tmp, newest first, with the lines each fix touched.

wordexp with WRDE_REUSE and WRDE_APPEND may return uninitialized memory
CVE-2025-15281 · sysdeps/aarch64/memrchr.S · lines 79–106 · +11 −8
High · CVSS 7.5
EPSS 0.5%2026-01-20
wordexp with WRDE_REUSE and WRDE_APPEND may return uninitialized memory
CVE-2025-15281 · sysdeps/aarch64/strcpy.S · lines 104–108 · +0 −3
High · CVSS 7.5
EPSS 0.5%2026-01-20
CVE-2025-0395

CVE-2025-0395 · sysdeps/aarch64/memrchr.S · lines 79–106 · +11 −8

Medium · CVSS 6.2

EPSS 0.4%2025-01-22

CVE-2025-0395

CVE-2025-0395 · sysdeps/aarch64/strcpy.S · lines 104–108 · +0 −3

Medium · CVSS 6.2

EPSS 0.4%2025-01-22

Glibc: potential use-after-free in getaddrinfo()

CVE-2023-4806 · sysdeps/aarch64/memrchr.S · lines 79–106 · +11 −8

Medium · CVSS 5.9

EPSS 1.6%2023-09-18

Glibc: potential use-after-free in getaddrinfo()

CVE-2023-4806 · sysdeps/aarch64/strcpy.S · lines 104–108 · +0 −3

Medium · CVSS 5.9

EPSS 1.6%2023-09-18

Glibc: stack read overflow in getaddrinfo in no-aaaa mode

CVE-2023-4527 · sysdeps/aarch64/memrchr.S · lines 79–106 · +11 −8

Medium · CVSS 6.5

EPSS 1.7%2023-09-18

Glibc: stack read overflow in getaddrinfo in no-aaaa mode

CVE-2023-4527 · sysdeps/aarch64/strcpy.S · lines 104–108 · +0 −3

Medium · CVSS 6.5

EPSS 1.7%2023-09-18

Get an alert when the next CVE fix lands in debian/glibc, with the patched functions.

Monitor glibc CVEs

Other functions in these files

Functions in the same files that CVE fixes also changed.

1lensysdeps/aarch64/strcpy.S4 CVEs · 1 patches2023 to 2026

Other hotspots in the repository

Functions in debian/glibc changed by the most CVE fixes.

tmp19 CVEs · sysdeps/aarch64/memcpy.S __mips16_syscall15 CVEs · sysdeps/unix/sysv/linux/mips/mips32/mips16/mips16-syscall.h dstend5 CVEs · sysdeps/aarch64/memcpy.S __gconv_open5 CVEs · iconv/gconv_int.h len5 CVEs · sysdeps/aarch64/strnlen.S __volatile__5 CVEs · sysdeps/unix/sysv/linux/microblaze/sysdep.h

All patched functions in debian/glibc

Frequently asked questions

Common questions about CVE fixes to tmp.

How many CVEs have patched tmp?: 4 published CVEs changed tmp in debian/glibc, in 2 distinct patches totalling 88 changed lines, between 2023 and 2026.
What is the latest CVE that changed tmp?: CVE-2025-15281 (wordexp with WRDE_REUSE and WRDE_APPEND may return uninitialized memory), published 2026-01-20, changed lines 79 to 106 of sysdeps/aarch64/memrchr.S.
How does tmp compare to the rest of debian/glibc?: debian/glibc has 23 CVEs with a located fix in total; 4 of them changed tmp.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track debian/glibc CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing