CVE-2024-45021

memcg_write_event_control(): fix a user-triggerable oops

MEDIUM

5.5

CVSS Score

Published: September 11, 2024 at 03:13 PM UTC

Updated: August 5, 2026 at 12:04 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: memcg_write_event_control(): fix a user-triggerable oops we are *not* guaranteed that anything past the terminating NUL is mapped (let alone initialized with anything sane).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

2.6.34 ≤ v < 4.19.3212.6.34 ≤ v < 5.10.2252.6.34 ≤ v < 5.15.1662.6.34 ≤ v < 5.4.2832.6.34 ≤ v < 6.1.1072.6.34 ≤ v < 6.10.72.6.34 ≤ v < 6.112.6.34 ≤ v < 6.6.484.20 ≤ v < 5.4.2835.11 ≤ v < 5.15.1665.16 ≤ v < 6.1.1075.5 ≤ v < 5.10.2256.2 ≤ v < 6.6.486.7 ≤ v < 6.10.70dea116876eefc9c7ca9c5d74fe665481e499fa36.11 rc1 6.11 rc2 6.11 rc3

Vendor states this is fixed in 046667c4d3196938e992fba0dfcde570aa85cd0e (fixed)

Vendor states this is fixed in 0fbe2a72e853a1052abe9bc2b7df8ddb102da227 (fixed)

Vendor states this is fixed in 1b37ec85ad95b612307627758c6018cd9d92cca8 (fixed)

Vendor states this is fixed in 21b578f1d599edb87462f11113c5b0fc7a04ac61 (fixed)

Vendor states this is fixed in 43768fa80fd192558737e24ed6548f74554611d7 (fixed)

Vendor states this is fixed in ad149f5585345e383baa65f1539d816cd715fd3b (fixed)

Vendor states this is fixed in f1aa7c509aa766080db7ab3aec2e31b1df09e57c (fixed)

Vendor states this is fixed in fa5bfdf6cb5846a00e712d630a43e3cf55ccb411 (fixed)

Vendor states this is fixed in 2.6.34 (unaffected)

Vendor states this is fixed in 4.19.321 (unaffected)

Vendor states this is fixed in 5.10.225 (unaffected)

Vendor states this is fixed in 5.15.166 (unaffected)