CVE-2024-50302 @ Library

"CVE-2024-50302"
"linux_kernel-4.9.320-2"
"kernel_release (uname -r): 4.9.0-19-amd64"
"kernel_version (uname -v): #1 SMP Debian 4.9.320-2 (2022-06-30)"
"Debian kernel package: 4.9.320-2"
"Am I vulnerable?"

Status

new KEV

Priority

4.65

Match score

4.0

Risk

InfoLeak priv:user

CVSS

5.5 MEDIUM

Reason

cpe: linux_kernel; pkgs: linux_kernel; version: in-range: linux_kernel-4.9.320-2; KEV; risk:info_disclosure

Created

2026-10-15T10:19:59Z

Updated

2026-10-20T10:18:16Z

Package interrogation (copy)

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

Package	Commands
linux_kernel-4.9.320-2

Inventory lookup

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

Suggestions: linux_kernel

No packages matching “linux_kernel” in inventory.

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-2025-39964	7.8	KEV	morris, mufasa	reviewing	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 9 (stretch) (9) · debian

Arch

x86_64

kernel_release

uname -r → 4.9.0-19-amd64

kernel_version

uname -v → #1 SMP Debian 4.9.320-2 (2022-06-30)

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
Archive	new	3.83	2026-10-20T10:18:16Z	Open
Janus	new	3.83	2026-10-20T10:18:16Z	Open
Saiph	new	3.83	2026-10-20T10:18:16Z	Open

Description

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

HID: core: zero-initialize the report buffer

Since the report buffer is used by all kinds of drivers in various ways, let's
zero-initialize it during allocation to make sure that it can't be ever used
to leak kernel memory via specially-crafted report.

Update status

Add note only

References

NVD: CVE-2024-50302