CVE-2025-46805
published 2025-05-26CVE-2025-46805: Screen version 5.0.0 and older version 4 releases have a TOCTOU race potentially allowing to send SIGHUP, SIGCONT to privileged processes when installed…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.17%
6.2th percentile
Screen version 5.0.0 and older version 4 releases have a TOCTOU race potentially allowing to send SIGHUP, SIGCONT to privileged processes when installed setuid-root.
Affected
13 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | screen | < screen 4.9.1-3 (forky) | screen 4.9.1-3 (forky) |
| gnu | screen | >= 0 < 4.9.1-3 | 4.9.1-3 |
| gnu | screen | >= 0 < 4.9.1-3 | 4.9.1-3 |
| gnu | screen | >= 0 < 4.9.0-1ubuntu0.1 | 4.9.0-1ubuntu0.1 |
| gnu | screen | >= 0 < 4.9.1-1ubuntu1 | 4.9.1-1ubuntu1 |
| msrc | azl3_kernel_6.6.47.1-1_on_azure_linux_3.0 | — | — |
| msrc | azl3_kernel_6.6.51.1-5_on_azure_linux_3.0 | — | — |
| msrc | azure_linux_3.0_arm | — | — |
| msrc | azure_linux_3.0_x64 | — | — |
| msrc | cbl2_kernel_5.15.164.1-1_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_kernel_5.15.167.1-1_on_cbl_mariner_2.0 | — | — |
| msrc | cbl_mariner_2.0_arm | — | — |
| msrc | cbl_mariner_2.0_x64 | — | — |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvdv4.05.7MEDIUMCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
osv6.5MEDIUM
vendor_ubuntu6.5MEDIUM
vendor_debian5.7LOW
vendor_redhat5.7MEDIUM
vendor_msrc5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
screen vulnerabilities
osv·2026-01-26·CVSS 6.5
CVE-2023-24626 [MEDIUM] screen vulnerabilities
screen vulnerabilities
It was discovered that GNU Screen incorrectly handled signals when setuid
or setgid privileges were being used, which is not the default in Ubuntu.
A local attacker could use this issue to send privileged signals, possibly
leading to a denial of service. This issue only affected Ubuntu 22.04 LTS.
(CVE-2023-24626)
It was discovered that GNU Screen incorrectly handled PTY permissions. A
local attacker could possibly use this issue to connect to an unauthorized
screen session. (CVE-2025-46802)
It was discovered that GNU Screen incorrectly handled file access when
setuid privileges were being used, which is not the default in Ubuntu. A
local attacker could use this issue to deduce information about certain
file paths. (CVE-2025-46804)
It was discovered that GNU Scree
GHSA
GHSA-v9hv-wgmv-7qj2: Screen version 5
ghsa_unreviewed·2025-05-26
CVE-2025-46805 [MEDIUM] CWE-367 GHSA-v9hv-wgmv-7qj2: Screen version 5
Screen version 5.0.0 and older version 4 releases have a TOCTOU race potentially allowing to send SIGHUP, SIGCONT to privileged processes when installed setuid-root.
OSV
CVE-2025-46805: Screen version 5
osv·2025-05-26·CVSS 5.7
CVE-2025-46805 [MEDIUM] CVE-2025-46805: Screen version 5
Screen version 5.0.0 and older version 4 releases have a TOCTOU race potentially allowing to send SIGHUP, SIGCONT to privileged processes when installed setuid-root.
Ubuntu
GNU Screen vulnerabilities
vendor_ubuntu·2026-01-26·CVSS 6.5
CVE-2023-24626 [MEDIUM] GNU Screen vulnerabilities
Title: GNU Screen vulnerabilities
Summary: Several security issues were fixed in GNU Screen.
It was discovered that GNU Screen incorrectly handled signals when setuid
or setgid privileges were being used, which is not the default in Ubuntu.
A local attacker could use this issue to send privileged signals, possibly
leading to a denial of service. This issue only affected Ubuntu 22.04 LTS.
(CVE-2023-24626)
It was discovered that GNU Screen incorrectly handled PTY permissions. A
local attacker could possibly use this issue to connect to an unauthorized
screen session. (CVE-2025-46802)
It was discovered that GNU Screen incorrectly handled file access when
setuid privileges were being used, which is not the default in Ubuntu. A
local attacker could use this issue to deduce information about
Red Hat
screen: Race Conditions when Sending Signals
vendor_redhat·2025-05-12·CVSS 5.7
CVE-2025-46805 [MEDIUM] CWE-362 screen: Race Conditions when Sending Signals
screen: Race Conditions when Sending Signals
Screen version 5.0.0 and older version 4 releases have a TOCTOU race potentially allowing to send SIGHUP, SIGCONT to privileged processes when installed setuid-root.
A flaw was found in Screen. A possible denial of service caused by race conditions when sending signals exists. The `CheckPid()` function drops privileges to the real user ID and tests whether the kernel can send a signal to the target PID using these credentials. The signal is sent later via `Kill()`, potentially using full root privileges. By this time, the previously checked PID could have been replaced by a different, privileged process. It might also be possible to trick the privileged Screen daemon process into sending signals to itself since a process is always allowed to s
Debian
CVE-2025-46805: screen - Screen version 5.0.0 and older version 4 releases have a TOCTOU race potentiall...
vendor_debian·2025·CVSS 5.7
CVE-2025-46805 [MEDIUM] CVE-2025-46805: screen - Screen version 5.0.0 and older version 4 releases have a TOCTOU race potentiall...
Screen version 5.0.0 and older version 4 releases have a TOCTOU race potentially allowing to send SIGHUP, SIGCONT to privileged processes when installed setuid-root.
Scope: local
bookworm: open
bullseye: open
forky: resolved (fixed in 4.9.1-3)
sid: resolved (fixed in 4.9.1-3)
trixie: resolved (fixed in 4.9.1-3)
Microsoft
drm/amdgpu: fix the waring dereferencing hive
vendor_msrc·2024-09-10·CVSS 5.5
CVE-2024-46805 [MEDIUM] CWE-476 drm/amdgpu: fix the waring dereferencing hive
drm/amdgpu: fix the waring dereferencing hive
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
Linux: Linux
Customer Action Required: Yes
Remediation: CBL-Mariner Releases
Reference: https://learn.microsoft
No detection rules found.
No public exploits indexed.
2025-05-26
Published