CVE-2024-42068 json
bpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()
published 2024-07-29 2 y ago modified 2026-10-21 19 d ago also EUVD-2024-39900
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
bpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()
set_memory_ro() can fail, leaving memory unprotected.
Check its return and take it into account as an error.
Patch / fix
- Linux Linux 5.15.162, 6.1.97, 6.6.160, 6.9.8, 6.10
- linux Debian 12 6.1.98-1
- linux Debian 14, Debian 13 6.9.8-1
debian advisories DEBIAN-CVE-2024-42068
- linux Ubuntu 20.04 LTS 5.4.0-202.222
- linux Ubuntu 22.04 LTS 5.15.0-121.131
- linux Ubuntu 24.04 LTS 6.8.0-48.48
- linux-aws Ubuntu 20.04 LTS 5.4.0-1136.146
- linux-aws Ubuntu 22.04 LTS 5.15.0-1069.75
- linux-aws Ubuntu 24.04 LTS 6.8.0-1018.20
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1140.149
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1068.76
ubuntu advisories UBUNTU-CVE-2024-42068
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/a359696856ca9409fb97655c5a8ef0f549cb6e03 commit
- git.kernel.org/stable/c/e4f602e3ff749ba770bf8ff10196e18358de6720 commit
- git.kernel.org/stable/c/2bbfffa802adc30b772d0e0f881a13c3804a965c commit
- git.kernel.org/stable/c/05412471beba313ecded95aa17b25fe84bb2551a commit
- git.kernel.org/stable/c/7d2cc63eca0c993c99d18893214abf8f85d566d8 commit
- git.kernel.org/stable/c/fdd411af8178edc6b7bf260f8fa4fba1bedd0a6d commit
- git.kernel.org/stable/c/e3540e5a7054d6daaf9a1415a48aacb092112a89 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-42068 updated cvss 4.4
kernel: bpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()
-
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 moreaffected: no fix planned “Out of support scope”
-
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 moreaffected: no fix available “Fix deferred”
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.30% chance of exploitation in the next 30 days, higher than 23% 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
- Weakness
-
- CWE-252 Unchecked Return Value
- Technology feeds
References
-
git.kernel.org
/stable/c/a359696856ca9409fb97655c5a8ef0f549cb6e03
patch
-
git.kernel.org
/stable/c/e4f602e3ff749ba770bf8ff10196e18358de6720
patch
- git.kernel.org /stable/c/2bbfffa802adc30b772d0e0f881a13c3804a965c
-
git.kernel.org
/stable/c/05412471beba313ecded95aa17b25fe84bb2551a
patch
-
git.kernel.org
/stable/c/7d2cc63eca0c993c99d18893214abf8f85d566d8
patch
-
git.kernel.org
/stable/c/fdd411af8178edc6b7bf260f8fa4fba1bedd0a6d
patch
-
git.kernel.org
/stable/c/e3540e5a7054d6daaf9a1415a48aacb092112a89
patch
- lists.debian.org /debian-lts-announce/2025/01/msg00001.html
Sources
- CVE List CVE-2024-42068
- NVD CVE-2024-42068
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.