CVE-2022-48619 is a moderate-severity denial-of-service flaw in the Linux kernel input subsystem's input_set_capability() function. The function failed to validate event codes against the bitmap bounds for the specified event type, allowing a low-privileged local attacker to cause a kernel panic. Red Hat assigned a CVSS v3.1 score of 5.5, reflecting high availability impact with no confidentiality or integrity impact.
Upstream fixed the defect in Linux kernel 5.17.10 through commit 409353cbe9fe48f6bc196114c442b1cff05a39bc, which adds per-event-type maximum-code validation and rejects invalid values. Red Hat remediated affected RHEL 8 kernel and kernel-rt packages through advisories RHSA-2024:7000 and RHSA-2024:7001; RHEL 9 variants are not affected, while RHEL 6 and 7 are outside support scope.

See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
Red Hat released RHSA-2024:7000 for the RHEL 8 kernel and RHSA-2024:7001 for the RHEL 8 kernel-rt, addressing CVE-2022-48619. The flaw could allow a low-privileged local attacker to panic the kernel through an out-of-range input event code.
Linux commit 409353cbe9fe48f6bc196114c442b1cff05a39bc added per-event-type maximum-code validation in input_set_capability(). Invalid event codes are logged and rejected rather than being used to set a capability.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
bugzilla.redhat.com
Open sourceredhat.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.