7.8

CVE-2024-40974: linux Out-of-bounds Write

CVSS: 7.8v3.1HighModified
AliasesUBUNTU-CVE-2024-40974DEBIAN-CVE-2024-40974
Published 12-07-2024Last modified 05-08-2026

Vulnerability summary

CVE-2024-40974 is a high (CVSS 7.8) Out-of-bounds Write vulnerability in linux. EPSS estimates a 0.30% chance of exploitation in the next 30 days, higher than 21.5% of scored vulnerabilities.

Overall risk
31/100
0100
Medium · default modelHow is this calculated?
CVSS score
7.8/10
010
High · v3.1 (CVE.org)
EPSS score
0.30%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 23 · Related 19

Timeline

  1. 12-07-2024
    PublishedVulnerability first disclosed.
  2. 05-08-2026
    Last modifiedVulnerability information updated.

Description

In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries: Enforce hcall result buffer validity and size plpar_hcall(), plpar_hcall9(), and related functions expect callers to provide valid result buffers of certain minimum size. Currently this is communicated only through comments in the code and the compiler has no idea. For example, if I write a bug like this: long retbuf[PLPAR_HCALL_BUFSIZE]; // should be PLPAR_HCALL9_BUFSIZE plpar_hcall9(H_ALLOCATE_VAS_WINDOW, retbuf, ...); This compiles with no diagnostics emitted, but likely results in stack corruption at runtime when plpar_hcall9() stores results past the end of the array. (To be clear this is a contrived example and I have not found a real instance yet.) To make this class of error less likely, we can use explicitly-sized array parameters instead of pointers in the declarations for the hcall APIs. When compiled with -Warray-bounds[1], the code above now provokes a diagnostic like this: error: array argument is too small; is of size 32, callee requires at least 72 [-Werror,-Warray-bounds] 60 | plpar_hcall9(H_ALLOCATE_VAS_WINDOW, retbuf, | ^ ~~~~~~ [1] Enabled for LLVM builds but not GCC for now. See commit 0da6e5fd6c37 ("gcc: disable '-Warray-bounds' for gcc-13 too") and related changes.

CVSS metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

0.30%

Chance of exploitation in the next 30 days

Percentile

22%

Versus all other CVEs

30-day change

0.00 pp

From 0.30% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.30%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Ubuntu129 products
  • linuxAll versions (No fix recorded) | < 5.4.0-195.215 | < 5.15.0-121.131 | < 6.8.0-44.44
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 5.4.0-1132.142 | < 5.15.0-1069.75 | < 6.8.0-1015.16
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Linux2 products
  • linux≥ b9377ffc3a03cde558d76349a262a1adbb6d3112, < acf2b80c31c37acab040baa3cf5f19fbd5140b18 | ≥ b9377ffc3a03cde558d76349a262a1adbb6d3112, < 19c166ee42cf16d8b156a6cb4544122d9a65d3ca | ≥ b9377ffc3a03cde558d76349a262a1adbb6d3112, < a8c988d752b3d98d5cc1e3929c519a55ef55426c | ≥ b9377ffc3a03cde558d76349a262a1adbb6d3112, < 262e942ff5a839b9e4f3302a8987928b0c8b8a2d | ≥ b9377ffc3a03cde558d76349a262a1adbb6d3112, < 8aa11aa001576bf3b00dcb8559564ad7a3113588 | ≥ b9377ffc3a03cde558d76349a262a1adbb6d3112, < 3ad0034910a57aa88ed9976b1431b7b8c84e0048 | ≥ b9377ffc3a03cde558d76349a262a1adbb6d3112, < aa6107dcc4ce9a3451f2d729204713783b657257 | ≥ b9377ffc3a03cde558d76349a262a1adbb6d3112, < ff2e185cf73df480ec69675936c4ee75a445c3e4 | 2.6.19
  • linux_kernel< 4.19.317 | ≥ 4.20, < 5.4.279 | ≥ 5.5, < 5.10.221 | ≥ 5.11, < 5.15.162 | ≥ 5.16, < 6.1.96 | ≥ 6.2, < 6.6.36 | ≥ 6.7, < 6.9.7
Debian1 product
  • linux< 6.1.99-1 | < 6.9.7-1

3 vendors · 132 products

References

32 links
Show all 32 references