CVE-2025-39964 @ Janus

"CVE-2025-39964"
"linux_kernel-4.19.316-1"
"kernel_release (uname -r): 4.19.0-27-amd64"
"kernel_version (uname -v): #1 SMP Debian 4.19.316-1 (2024-06-25)"
"Debian kernel package: 4.19.316-1"
"Am I vulnerable?"

Status

not_applicable KEV

Priority

4.17

Match score

4.0

Risk

Other priv:user

CVSS

7.8 HIGH

Reason

cpe: linux_kernel; pkgs: linux_kernel; version: in-range: linux_kernel-4.19.316-1; KEV

Created

2026-09-19T10:15:34Z

Updated

2026-10-20T10:16:57Z

Closed

2026-09-22T13:37:35Z

Package interrogation (copy)

Run on the host — click to copy a command. Debian/apt

Package	Commands
linux_kernel-4.19.316-1

Inventory lookup

Search package inventory across systems, then return here. Create a ticket on systems the matcher missed.

Suggestions: linux_kernel

Same product CVEs in your queue

Other open tickets that look like the same product. Closed tickets are omitted unless they are already pegged to this CVE.

CVE	CVSS	KEV	Systems	Status	Matched	Already related
CVE-2026-53266	8.8	KEV	Archive	reviewing	linux_kernel	—
CVE-2024-50302	5.5	KEV	Archive, Janus, Library, Saiph	new	linux_kernel	—

Related CVE (same fix)

Point this ticket’s CVE at a higher-priority / same-fix primary so you only triage one.

Host OS / kernel

Debian GNU/Linux 10 (buster) (10) · debian

Arch

x86_64

kernel_release

uname -r → 4.19.0-27-amd64

kernel_version

uname -v → #1 SMP Debian 4.19.316-1 (2024-06-25)

For Linux kernel CVEs, kernel_version (Debian packaging / build string) often decides fixed vs not; kernel_release is used for upstream NVD range compares.

Same CVE on other hosts

Open the ticket for this CVE on another system.

System	Status	Priority	Updated
morris	reviewing	10.8	2026-10-20T10:16:57Z	Open
mufasa	reviewing	10.8	2026-10-20T10:16:57Z	Open
Library	not_applicable	5.34	2026-10-20T10:16:57Z	Open
Archive	not_applicable	4.17	2026-10-20T10:16:57Z	Open
Saiph	not_applicable	4.17	2026-10-20T10:16:57Z	Open

Description

In the Linux kernel, the following vulnerability has been resolved:

crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg

Issuing two writes to the same af_alg socket is bogus as the
data will be interleaved in an unpredictable fashion.  Furthermore,
concurrent writes may create inconsistencies in the internal
socket state.

Disallow this by adding a new ctx->write field that indiciates
exclusive ownership for writing.

Determination

No local users

Update status

Add note only

Mitigation log

2026-09-22T13:37:35Z — not_applicable

No local users

References

NVD: CVE-2025-39964