CVE-2024-56706 | s390/cpum_sf: Fix and protect memory allocation of SDBs with mutex

In the Linux kernel, the following vulnerability has been resolved: s390/cpum_sf: Fix and protect memory allocation of SDBs with mutex Reservation of the PMU hardware is done at first event creation and is protected by a pair of mutex_lock() and mutex_unlock(). After reservation of the PMU hardware the memory required for the PMUs the event is to be installed on is allocated by allocate_buffers() and alloc_sampling_buffer(). This done outside of the mutex protection. Without mutex protection two or more concurrent invocations of perf_event_init() may run in parallel. This can lead to allocation of Sample Data Blocks (SDBs) multiple times for the same PMU. Prevent this and protect memory allocation of SDBs by mutex.

Published: 2024-12-28 Last update: 2025-09-26 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-56706 is rated Low Risk (29/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.04%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-56706

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2024-12-29 — 0.04% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-56706

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.3 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.0 5.2 [email protected]

Weakness enumeration for CVE-2024-56706

OS Trackers for CVE-2024-56706

vendor priority summary link
debian unimportant CVE-2024-56706 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-56706
redhat low — https://access.redhat.com/security/cve/CVE-2024-56706
suse medium CVE-2024-56706 severity moderate: SUSE including 52 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 331 product×package rows across 58 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 12 SP5, … (58 product lines)): Known Not Affected 305, Fixed 26. https://www.suse.com/security/cve/CVE-2024-56706/
ubuntu medium CVE-2024-56706 medium priority: Ubuntu including 126 source packages (linux, linux-allwinner-5.19, …), 1008 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): DNE 690, ignored 146, not-affected 113, released 59. https://ubuntu.com/security/CVE-2024-56706

Affected software / configurations for CVE-2024-56706

Vendor Product Version Raw CPE
linux linux_kernel >= 6.12, < 6.12.2 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

References for CVE-2024-56706

cvelogic Threat Intelligence