CVE-2024-56720: bpf, sockmap: Several fixes to bpf_msg_pop_data
In the Linux kernel, the following vulnerability has been resolved:
bpf, sockmap: Several fixes to bpf_msg_pop_data
Several fixes to bpf_msg_pop_data,
1. In sk_msg_shift_left, we should put_page
2. if (len == 0), return early is better
3. pop the entire sk_msg (last == msg->sg.size) should be supported
4. Fix for the value of variable "a"
5. In sk_msg_shift_left, after shifting, i has already pointed to the next
element. Addtional sk_msg_iter_var_next may result in BUG.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux kernel BPF sockmap message handling can mishandle memory and message boundaries. A local user with limited privileges may be able to trigger serious confidentiality, integrity, or availability impacts. Internet-based exploitation is not indicated by the supplied CVSS vector.
Executive priority
Treat this as a high-priority kernel update for systems allowing low-privileged local access. Prioritize broadly shared or sensitive hosts. The absence of documented active exploitation lowers emergency pressure, but potential impact spans confidentiality, integrity, and availability.
Technical view
CVE-2024-56720 affects bpf_msg_pop_data and related sk_msg_shift_left logic. Reported defects include a missing put_page, zero-length handling, failure to support full-message removal, an incorrect variable value, and an extra iterator advance that may trigger a kernel BUG. It is classified as CWE-401 with CVSS 3.1 score 7.8.
Likely exposure
Exposure is limited to Linux kernels containing the vulnerable code where a low-privileged local actor can reach the affected BPF sockmap path. The supplied affected-version list is ambiguous and includes raw revisions, so distribution kernels and backports require vendor-specific verification.
Exploitation context
The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction. The supplied record is not in CISA KEV and provides no evidence of active exploitation or a public exploit. The precise exploitation primitive is not established by these sources.
Researcher notes
The record groups several correctness fixes into one CVE. Missing page release supports the CWE-401 classification, while iterator and boundary defects may cause a kernel BUG. The bundle does not establish whether every defect independently enables all CVSS impacts. Exact affected ranges cannot be reconstructed confidently from the flattened version data.
Mitigation direction
Install a vendor kernel containing the applicable stable fix for CVE-2024-56720.
Consult distribution advisories because vendor kernels may contain backported fixes without matching upstream version numbers.
Activate the updated kernel using the vendor's documented maintenance procedure.
Reduce unnecessary local account access while affected systems await remediation.
Validation and detection
Inventory running kernel builds, including distribution release and package revision.
Check vendor changelogs for CVE-2024-56720 or the applicable upstream stable commit.
Confirm the remediated kernel is running after maintenance, not merely installed.
Review kernel crash records for BPF or sockmap faults, recognizing they do not prove exploitation.
Identify systems where low-privileged local users can reach BPF sockmap functionality.
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.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.