CVE-2024-44966 json
binfmt_flat: Fix corruption when not offsetting data start
published 2024-09-04 2 y ago modified 2026-08-05 3 mo ago also EUVD-2024-41168
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
binfmt_flat: Fix corruption when not offsetting data start
Commit 04d82a6d0881 ("binfmt_flat: allow not offsetting data start") introduced a RISC-V specific variant of the FLAT format which does not allocate any space for the (obsolete) array of shared library pointers. However, it did not disable the code which initializes the array, resulting in the corruption of sizeof(long) bytes before the DATA segment, generally the end of the TEXT segment.
Introduce MAX_SHARED_LIBS_UPDATE which depends on the state of CONFIG_BINFMT_FLAT_NO_DATA_START_OFFSET to guard the initialization of the shared library pointer region so that it will only be initialized if space is reserved for it.
Patch / fix
- Linux Linux 5.15.165, 6.1.106, 6.6.47, 6.10.6, 6.11
- linux Debian 12 6.1.106-1
- linux Debian 14, Debian 13 6.10.6-1
debian advisories DEBIAN-CVE-2024-44966
- linux Ubuntu 22.04 LTS 5.15.0-125.135
- linux Ubuntu 24.04 LTS 6.8.0-50.51
- linux-aws Ubuntu 22.04 LTS 5.15.0-1072.78
- linux-aws Ubuntu 24.04 LTS 6.8.0-1020.22
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1071.79
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1019.21
- linux-gke Ubuntu 22.04 LTS 5.15.0-1069.75
- linux-gke Ubuntu 24.04 LTS 6.8.0-1015.19
ubuntu advisories UBUNTU-CVE-2024-44966
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/3a684499261d0f7ed5ee72793025c88c2276809c commit
- git.kernel.org/stable/c/af65d5383854cc3f172a7d0843b628758bf462c8 commit
- git.kernel.org/stable/c/49df34d2b7da9e57c839555a2f7877291ce45ad1 commit
- git.kernel.org/stable/c/9350ba06ee61db392c486716ac68ecc20e030f7c commit
- git.kernel.org/stable/c/3eb3cd5992f7a0c37edc8d05b4c38c98758d8671 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-44966 updated cvss 6.1
kernel: binfmt_flat: Fix corruption when not offsetting data start
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/3a684499261d0f7ed5ee72793025c88c2276809c
patch
-
git.kernel.org
/stable/c/af65d5383854cc3f172a7d0843b628758bf462c8
patch
-
git.kernel.org
/stable/c/49df34d2b7da9e57c839555a2f7877291ce45ad1
patch
-
git.kernel.org
/stable/c/9350ba06ee61db392c486716ac68ecc20e030f7c
patch
-
git.kernel.org
/stable/c/3eb3cd5992f7a0c37edc8d05b4c38c98758d8671
patch
- lists.debian.org /debian-lts-announce/2025/01/msg00001.html
Sources
- CVE List CVE-2024-44966
- NVD CVE-2024-44966
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.