CVE-2024-42068: bpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()
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.
Security readout for executives and security teams
Plain-English summary
A Linux kernel BPF protection routine failed to check whether memory was successfully made read-only. If that operation failed, program memory could remain unprotected. The CVSS assessment describes a local, low-privilege attack requiring no user interaction, with potentially high confidentiality, integrity, and availability impact.
Executive priority
Treat this as a high-priority kernel update within the normal high-severity patch window. Prioritize systems permitting local accounts or less-trusted workloads. The potential impact is substantial, but the supplied evidence does not justify an active-exploitation emergency designation.
Technical view
bpf_prog_lock_ro() did not account for set_memory_ro() failure. The correction checks its return and treats failure as an error, preventing silent continuation with unprotected memory. CVSS v3.1 is 7.8: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. No CWE is supplied.
Likely exposure
Exposure is limited to systems running affected Linux kernels where the vulnerable BPF path is reachable. The bundle lists several version values, including 3.18, 5.15.162, 6.1.97, 6.9.8, and 6.10, but does not clearly preserve their range relationships. Confirm status through distribution package mappings.
Exploitation context
The supplied bundle marks KEV false and provides no evidence of active exploitation or a public exploit. The CVSS vector indicates a local attacker with low privileges, low attack complexity, and no user interaction. Configuration-specific prerequisites are not documented in the supplied sources.
Researcher notes
The defect concerns unchecked failure while applying read-only protection to BPF program memory. Upstream stable commits document the correction, but the supplied data does not establish exploitation mechanics, affected configuration requirements, or complete version-range semantics. Distribution backports may make kernel version strings alone insufficient for determining vulnerability.
Mitigation direction
Upgrade to a vendor kernel release containing the applicable stable fix for CVE-2024-42068.
Consult Linux distribution guidance to map packaged kernels to the referenced upstream fixes.
If updates are unavailable, seek vendor guidance; the sources provide no alternative workaround.
Reboot affected systems into the updated kernel according to normal change-control procedures.
Validation and detection
Inventory installed and actively running kernel versions across Linux systems.
Compare distribution package revisions with vendor advisories and the referenced stable commits.
Confirm systems are running the updated kernel after maintenance or reboot.
Record unresolved systems where version-range or backport status cannot be established.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-42068 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.